Agent-native · MCP + HTTP
Make every agent check the lane before it scaffolds
One tool, crowding_check(idea): 8 supply + 3 demand adapters, confidence, Supply × Demand quadrant, wedges and a tamper-evident receipt (issuer-authenticated only when signing and an independent pin are configured). Stateless Streamable HTTP — no install, no API key for the free tier.
1 · Add the MCP server (Cursor .cursor/mcp.json / Claude Code / Windsurf / goose)
{
"mcpServers": {
"simultaneity": { "url": "https://frontier-oss-ideas.vercel.app/api/mcp" }
}
}Claude Code: claude mcp add --transport http simultaneity https://frontier-oss-ideas.vercel.app/api/mcp
1b · Windsurf, goose, OpenHands and stdio-only clients
Windsurf (~/.codeium/windsurf/mcp_config.json):
{
"mcpServers": {
"simultaneity": { "serverUrl": "https://frontier-oss-ideas.vercel.app/api/mcp" }
}
}goose (~/.config/goose/config.yaml):
extensions:
simultaneity:
name: simultaneity
type: streamable_http
uri: https://frontier-oss-ideas.vercel.app/api/mcp
enabled: true
timeout: 60OpenHands (config.toml):
[mcp] shttp_servers = ["https://frontier-oss-ideas.vercel.app/api/mcp"]
Clients that only speak stdio: run the zero-dependency bridge from a clone of the repo.
{
"mcpServers": {
"simultaneity": {
"command": "node",
"args": ["bin/simultaneity-mcp.mjs"],
"env": { "SIMULTANEITY_API_URL": "https://frontier-oss-ideas.vercel.app" }
}
}
}2 · Auto-trigger it (CLAUDE.md / AGENTS.md / .cursorrules)
Before scaffolding any new project or feature idea, call the simultaneity crowding_check tool with a one-line description. If the verdict is Crowded or Saturated, propose a wedge before writing code.
3 · Or plain HTTP
curl "https://frontier-oss-ideas.vercel.app/api/search?q=AI+code+review+agent"
curl -X POST https://frontier-oss-ideas.vercel.app/api/mcp -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"crowding_check","arguments":{"idea":"AI code review agent"}}}'Why this vs other idea-check MCPs
- Eight supply sources incl. arXiv, OpenAlex and Hugging Face — plus three demand channels.
- Confidence + coverage math, visible degraded-source warnings, published methodology & gold-set calibration.
- Tamper-evident receipts (SHA-256, Ed25519 when configured) — verify at POST /api/verify.