The Forgeby MCP server.
One endpoint, three read-only tools, three reference resources and three prompts. Company-level European market data for AWS partners. This page is the documentation the server itself points at when it answers you.
https://db.forgeby.com/functions/v1/forgeby-mcpFor paying partners. The handshake stays open.
initialize and ping answer without a token, so a client can
complete the protocol handshake and read a proper error instead of hitting a dead socket. Every
method that returns data needs a bearer token from a forgeby.com account whose workspace holds an
activated zone.
{"jsonrpc":"2.0","id":1,"error":{"code":-32001,
"message":"Forgeby's MCP is for paying partners. Sign in at forgeby.com,
activate a zone, and pass your bearer token as
Authorization: Bearer <token>.",
"data":{"auth":"bearer","docs":"https://forgeby.com/mcp"}}}-32002 means the token is good but the
workspace has no activated zone. The 14-day full-access window covers the product, not this API.
A zone is priced when we open.Nothing here can act.
| Tool | Arguments | Returns |
|---|---|---|
| forgeby_name_market | country, optional icp |
Company count for the market, cloud mix by named vendor, the play split (Migrate, Build, Expand) and size bands. |
| forgeby_read_company | domain_or_orgnr |
One company: measured cloud vendor with the evidence that produced it, the play its estate fits, size band, and a 90-day signal count. |
| forgeby_capabilities | none | Machine-readable self-description: what this tier serves and what it withholds. |
Resources: forgeby://zones (the zones we sell),
forgeby://method (how the numbers are made), forgeby://funded-doors (the play
taxonomy, in AWS’s own field names). Prompts: read a market, qualify one account, brief a partner
on a zone they do not sell into yet. Resources are passive reference and prompts are templates:
neither touches a system.
The limits are in the protocol, not the prose.
No person, ever
No individual-level data is returned and none is read. This server touches no contact table. People are revealed only inside the app, where the metering and the Article 14 posture live.
No acting operation exists
All three tools are reads. Nothing here can send, file, submit or write. Outreach and Partner Central writes happen elsewhere, drafted for a named human and sent by that human.
Nightly, never live
Every figure comes from a nightly batch read of public registers and our own network measurements, and carries the date it was counted. A number here was true when it was counted, not when you asked.
A shape is not an eligibility
A play says what an account looks like, not what AWS will fund. Funding needs a scoped project, a budget and your own AWS team.
The same statements are served machine-readably on every
initialize, in the x-agentic-access block, so an agent can learn what this
surface refuses to do before it connects rather than after.
Claude, Cursor, or anything that speaks MCP.
{
"mcpServers": {
"forgeby": {
"type": "http",
"url": "https://db.forgeby.com/functions/v1/forgeby-mcp",
"headers": { "Authorization": "Bearer <your token>" }
}
}
}Also here for machines: /openapi.json · /llms.txt · /llms-full.txt · this page as Markdown. The AI at the front of this product is Rune, openly an AI, with a signed identity passport.