01 · How it works · One agent, one toolFictional names · .example domains
01The agent knows the tool. It needs the facts.
Requestpaid · x402
get_node({
"slug": "acme-insight"
})Node · get_node
Acme Insight
acme-insight · tool- MCP server
- mcp.acme.example/mcp
docs.acme.example/mcp · Connect any MCP client to mcp.acme.example/mcp
· captured 16 Oct 2026- API
- Public · OAuth 2.0
docs.acme.example/api/auth · Requests are authorised with OAuth 2.0
· captured 16 Oct 2026- Webhooks
- Outbound
docs.acme.example/webhooks · We send events to an endpoint you choose
· captured 16 Oct 2026- Plans
- Free, Pro, Business
acme.example/pricing · Choose Free, Pro or Business
· captured 16 Oct 2026- Clients
- 4 stated
docs.acme.example/mcp#clients · Tested with the following clients
· captured 16 Oct 2026
Raw response · abbreviated
{
"slug": "acme-insight",
"mcp_server": {
"value": "mcp.acme.example/mcp",
"citation": { "url": "docs.acme.example/mcp", "span": "Connect any MCP client…", "captured": "2026-10-16" }
},
"api": { "value": "public", "auth": "oauth2", "citation": { … } },
…
}
02Does it work with the CMS the user already runs?
Requestpaid · x402
verify_edge({
"source": "acme-insight",
"dest": "quill-cms"
})Edge · verify_edge
Acme Insight ↔ Quill CMS
E·02 · native · bidirectional- Found
- Yes
acme.example/integrations/quill · Acme Insight for Quill CMS
· captured 16 Oct 2026- Mechanism
- native_direct
docs.acme.example/integrations/quill · Built in. No middleware required
· captured 16 Oct 2026- Direction
- bidirectional
docs.acme.example/integrations/quill#sync · Changes sync in both directions
· captured 16 Oct 2026- Data
- Produces web_content, documents · Consumes web_content, documents
docs.acme.example/integrations/quill#data · Pages and documents move between both tools
· captured 16 Oct 2026- Interaction
- data_sync · trigger_action
docs.acme.example/integrations/quill#actions · Sync content and trigger actions
· captured 16 Oct 2026- Timing
- On publish
docs.acme.example/integrations/quill#timing · Runs each time a page is published
· captured 16 Oct 2026
Requestpaid · x402
verify_edge({
"source": "acme-insight",
"dest": "harbor-cdn"
})Edge · verify_edge
Harbor CDN → Acme Insight
E·03 · api · dest_to_source- Found
- Yes
acme.example/integrations/harbor · Acme Insight for Harbor CDN
· captured 16 Oct 2026- Mechanism
- api_pull
docs.acme.example/integrations/harbor · Acme Insight pulls from the Harbor API
· captured 16 Oct 2026- Direction
- dest_to_source
docs.acme.example/integrations/harbor#flow · Data flows from Harbor into Acme Insight
· captured 16 Oct 2026- Data
- Consumes logs
docs.acme.example/integrations/harbor#data · Reads your edge logs
· captured 16 Oct 2026- Interaction
- data_sync
docs.acme.example/integrations/harbor#sync · Logs are synced on a schedule
· captured 16 Oct 2026
04Can the user’s assistant reach it, and on which plan?
Requestpaid · x402
get_edges({
"slug": "acme-insight",
"type": "mcp"
})Edge · get_edges · mcp
Acme Insight · MCP
E·04 · mcp · vendor_published- Server
- mcp.acme.example/mcp
docs.acme.example/mcp · Connect any MCP client to mcp.acme.example/mcp
· captured 16 Oct 2026- Authority
- vendor_published
docs.acme.example/mcp · Our official MCP server
· captured 16 Oct 2026- Tools
- Visibility Reports (read) · Citations (read) · Action Center (read)
docs.acme.example/mcp#tools · The server exposes the following tools
· captured 16 Oct 2026- Plan required
- Pro
acme.example/pricing#mcp · MCP access is included on Pro
· captured 16 Oct 2026- Clients
- Nebula Chat, Orbit Code, Quill Assistant, Lumen IDE
docs.acme.example/mcp#clients · Tested with the following clients
· captured 16 Oct 2026
A few calls on one tool. Mechanism, direction, data, plan, operations - each cited to the vendor’s page.
Don’t know the tool yet? search_edges returns a shortlist. The depth is always per pair.