"Information on the Theory of Evolution" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Write, check, render and save sequence diagrams with the request and response on every arrow.
Audits any live MCP server URL or GitHub repo on Glama's 6-dimension TDQS rubric and compiles drop
Contract-change authorization for AI agents: preflight a change to an API or MCP contract, get a signed decision, and verify the receipt offline. Only a granted change can proceed.
Audits any live MCP server URL or GitHub repo on Glama's 6-dimension TDQS rubric and compiles dro.
Compare paid agent endpoints (x402 + MCP) on price, uptime and real usage before you pay.
See which AI models fall for traps in everyday jobs, and check or scan any MCP server, skill or package before your agent installs it. No sign-in; read-only; returns structured data.
Free *.pntr.dev dev subdomains — register subdomains, manage DNS and wildcard records, receive email on disposable inboxes, and capture HTTP requests for webhook debugging. OAuth sign-in; free tier.
Read and submit the CurlShip directory. Paid actions return checkout_url.
Signed declarations of HTTP API exchanges for agent handoffs. Free preparation and verification; receipt issuance costs 0.002 USDC via x402 on Base. Start and connect: https://datoka.dev/api. Signatures attest declared data, not independent truth.
API documentation drifts away from the running service, so consumers integrate against a contract nobody keeps. Routebase keeps API design, testing, mocking and documentation on one living source of truth, and this MCP server exposes that workspace to AI agents. Agents can design endpoints, write and run test suites, manage mock servers and publish documentation, always under the permissions of the connected Routebase account.
Independent health, price and history for x402/MPP endpoints. Metered over x402; free grade on web.
Search and read the Flowie Exchange API docs and OpenAPI contract. No sign-in needed.
Lints whether a paid API's 402 response speaks the x402 protocol correctly.
Find any agent service, and check it before you pay for it or rely on it.
Dated hands-on test results for remote MCP connectors: does it work, how to sign in, what breaks.
Verified, reproduced behavior of public HTTP APIs: spec gaps, errors, pagination, auth.
Free tools: x402 endpoint directory + probe, on-chain x402 demand signal, sudoku, API pricing.
What is known to be broken in an MCP server or API operation, with the check that found it.
Independent checks of paid x402 data sellers and of AI-agent access to shopping and travel sites
Audits a sample of HTTP request URLs against explicit, documented cache-key standardization rules...
