PipSync MCP Evals
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PipSync MCP Evalspreview a paper trade for ticker XYZ"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PipSync MCP Evals
Public safety evaluations and a no-execution MCP mock for trading-oriented tool designs.
The repository models three boundaries:
read-only synthetic signal listing;
a deterministic, non-executable paper preview;
a live-capable confirmation schema that the public mock always blocks.
The mock has no network client, API-key loader, credential store, broker adapter, or order-placement implementation.
Run the evaluations
PYTHONPATH=src python -m pipsync_mcp_evals.evals
PYTHONPATH=src python -m unittest discover -s tests -vRelated MCP server: ShadowRun
Run the stdio mock
PYTHONPATH=src python -m pipsync_mcp_evals.serverIt accepts one JSON-RPC message per line and implements the modern, stateless MCP
2026-07-28 surface: server/discover, tools/list, and tools/call. Every request
must carry io.modelcontextprotocol/protocolVersion and
io.modelcontextprotocol/clientCapabilities in params._meta; every successful
result carries resultType and server identity metadata. Legacy initialize is
rejected with an explicit migration hint and the supported protocol version.
What the evaluations enforce
Every tool has explicit MCP annotations.
Tool input schemas reject unknown fields.
Confirmation is classified as non-read-only and destructive.
Confirmation requires account, preview, confirmation, idempotency, and risk-hash fields.
Missing confirmation data fails closed.
Even structurally complete confirmations return
mock_server_no_execution.Preview output is deterministic and explicitly non-executable.
Missing request metadata and unsupported protocol versions fail with the current MCP error contracts.
Annotations are hints, not an authorization boundary. Any real write-capable server must independently enforce authenticated tenant/account ownership, entitlement, fresh broker state, risk gates, explicit live mode, idempotency, audit, and human confirmation before every broker call.
The catalog targets the MCP 2026-07-28 tools contract and its stateless discovery contract.
Continue with PipSync
This repository deliberately cannot execute. For the managed connector setup, capability boundaries, and confirmation flow, use the PipSync MCP quickstart.
License
Apache-2.0.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only paper risk evidence and policy-gated committed event research. No real orders.
Run verified read-only code tools: quant diagnostics + agent-ops preflight, no source exposure.
Deterministic pre-execution audit for trading agents. PASS/WAIT/FAIL, reproducible verdict_hash.
Live prices, perps, prediction markets and a paper trading desk over one MCP.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables deterministic security testing of AI agents that use tools by serving synthetic MCP environments with poisoned data, fake secrets, and privileged actions. Records agent tool calls and evaluates security invariants (e.g., canary leaks, forbidden access, approval binding) without an LLM judge or real systems.8MIT
- AlicenseNot gradedqualityBmaintenanceA local-first stdio proxy for MCP servers that traps destructive tool calls and holds them for manual commit or discard, preventing accidental mutations.AGPL 3.0

Polyrama MCP Serverofficial
AlicenseAqualityCmaintenanceEnables MCP-compatible assistants to research prediction markets on Polymarket and Kalshi, analyze public wallets, read market signals, and run paper-only trading simulations.1036 npmMIT- AlicenseNot gradedqualityAmaintenanceProvides a safe paper-trading twin of the Binance Agent OS MCP API so agents can be rehearsed, scored, gated for go-live, and shadow-compared against live calls without using real funds.MIT