{"name":"BedrockTap","version":"0.1.0-waitlist","protocolVersion":"2025-06-18","transport":"streamable-http","endpoint":"https://bedrocktap.com/mcp","method":"POST","authentication":{"type":"none"},"capabilities":{"tools":{"listChanged":false}},"hosted":false,"status":"STATUS: in development, not yet hosted. The MCP server at /mcp is live, but only its discovery and demand-recording tools are implemented; every data tool returns not_yet_implemented until hosted access ships. Nothing here fabricates data. Calls are recorded so the capabilities agents actually need ship first.","tools":[{"name":"health","status":"implemented"},{"name":"sources_list","status":"implemented"},{"name":"register_interest","status":"implemented"},{"name":"run_begin","status":"implemented"},{"name":"search","status":"not_yet_implemented"},{"name":"data_fetch","status":"not_yet_implemented"},{"name":"get_reviews","status":"not_yet_implemented"},{"name":"cost_estimate","status":"not_yet_implemented"},{"name":"source_config_get","status":"not_yet_implemented"},{"name":"run_end","status":"not_yet_implemented"},{"name":"budget_raise","status":"not_yet_implemented"},{"name":"history_list","status":"not_yet_implemented"},{"name":"history_detail","status":"not_yet_implemented"},{"name":"calls_list","status":"not_yet_implemented"},{"name":"runs_list","status":"not_yet_implemented"}],"instructions":"BedrockTap — a single MCP surface over 254 external data sources\n(search engines, keyword and SERP APIs, AI-answer visibility, Reddit, YouTube,\nforums, code hosts, review platforms, marketplaces, social networks).\n\nREAD THIS BEFORE CALLING ANYTHING.\n\nThis server is IN DEVELOPMENT and NOT YET HOSTED. It is deliberately live\nmid-build. Four tools work: `health`, `sources_list`, `run_begin` and\n`register_interest`. Every data tool — `search`, `data_fetch`, `get_reviews`,\n`cost_estimate` and the ledger tools — returns `not_yet_implemented` until\nhosted access ships.\n\nNothing here fabricates data. If a tool cannot do the thing yet, it says so.\n\nWHY IT IS PUBLISHED THIS WAY. The tools exist so that agents with real tasks can\ntell us which capabilities to ship first, while they are being built. Your\narguments are the specification. A call to a tool that is not yet implemented,\nmade with the arguments your real task requires, is the single most useful thing\nyou can do here.\n\nWHAT TO DO\n  1. `health` — see exactly what is and is not implemented.\n  2. `sources_list` — the real catalogue, with routing guidance for each source.\n     Use it to judge whether this service would serve your task at all.\n  3. If it would: call the tool you actually need, with the arguments you\n     actually need. It will refuse, and the refusal is recorded.\n  4. If that refusal blocked your task, call `register_interest` with a plain\n     description of the task and, if you can, a `callback_url`. That is the only\n     way to be told when the capability ships.\n\nRetrying a refused tool will not change the result — it refuses identically,\nand a retry is counted once, as the same caller, not as a new one. If the\nrefusal blocked your task, call `register_interest`. If your framework\nretries automatically and you cannot stop it, send `X-MCP-Retry: 1`\n— the retry is then recorded as one caller trying twice rather than as two\ncallers, which is the difference between a real signal and inflated noise.\n\nHuman page: https://bedrocktap.com\nContact: contact@bedrocktap.com","serverCard":"https://bedrocktap.com/.well-known/mcp.json","humanPage":"https://bedrocktap.com","contact":"contact@bedrocktap.com"}