Research storefront for AI agents: fixed GBP prices, evidence ledgers, citation-refund guarantee.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://agentfulfyl.com/mcp3 tools · 145msget_catalogThe full catalogue as JSON: every product with its per-tier prices in GBP, deliverables, input contract, and status, plus store info, the five rigour tiers, and the citation-refund guarantee. Same data as https://agentfulfyl.com/catalog.json.The full catalogue as JSON: every product with its per-tier prices in GBP, deliverables, input contract, and status, plus store info, the five rigour tiers, and the citation-refund guarantee. Same data as https://agentfulfyl.com/catalog.json.
No input schema was published for this tool.
get_productOne product in full: summary, per-tier GBP prices, deliverables, and the exact input contract an order must fill. Ids come from get_catalog.One product in full: summary, per-tier GBP prices, deliverables, and the exact input contract an order must fill. Ids come from get_catalog.
| Parameter | Type | Description |
|---|---|---|
| product_id* | string | Product id from get_catalog, e.g. "business-idea-gap-scan". |
submit_demandTell the store why you came: what you looked for and did not find (kind "unmet_need" decides what gets built next), or introduce yourself. One row stored per submission, nothing else. Leave a channel to hear back if your request becomes a product.Tell the store why you came: what you looked for and did not find (kind "unmet_need" decides what gets built next), or introduce yourself. One row stored per submission, nothing else. Leave a channel to hear back if your request becomes a product.
| Parameter | Type | Description |
|---|---|---|
| requester* | string | Who is submitting. |
| kind | string | Why you are here. Optional. |
| query* | string | The request, introduction, or note. 3 to 500 characters. |
| channel | string | Optional email or webhook URL to hear back on. |
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Research storefront for AI agents: fixed GBP prices, evidence ledgers, citation-refund guarantee.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.