MCP servers and WebMCP tools for company data
Answer in brief
An MCP server exposes an API's calls as tools that an AI application adds once. WebMCP lets a web page offer tools to the agent in the user's browser, with no setup. For company data both should wrap the same HTTP contract, so an agent gets the same records and IDs as your code, under a rate limit you can name.
Disclosure. This site is published by Coragrid, the operator of CompanyRegistryAPI.com, and promotes it. “Best” is our editorial choice, not a measured ranking. Other products are described only from their own official pages. How we choose
MCP in one paragraph
The Model Context Protocol specification describes MCP as an open protocol that connects LLM applications with external data sources and tools, using JSON-RPC 2.0 messages. A server publishes tools, each with a name, a description and an input schema; an AI application lists them and calls them on the user’s behalf.
WebMCP in one paragraph
The WebMCP draft says its API enables web applications to provide JavaScript tools to AI agents. The tools live in the page: when an agent in the browser opens it, it finds the tools and calls them instead of clicking through the interface.
How CompanyRegistryAPI.com offers both
From its own pages:
| MCP server | WebMCP tools | |
|---|---|---|
| Where | https://mcp.companyregistryapi.com/mcp |
Every CompanyRegistryAPI.com page, in a browser with WebMCP |
| Setup | Add the endpoint to an AI app once | None; the tools come with the page |
| Allowance | Its own allowances | The visitor’s address, 60 requests a minute |
| Tools | Same names, inputs and answers as WebMCP | search_companies, get_company |
| Answers | The free API’s JSON | The free API’s JSON |
Its WebMCP page names the ChatGPT desktop app’s built-in browser as a host
today, and Chrome 149+ and Edge 150+ once the site joins their WebMCP origin
trials; until then, chrome://flags/#enable-webmcp-testing turns it on in
Chrome for testing.
Registering a tool in your own page
If you build your own front end on a company data API, a WebMCP tool is a thin wrapper over a call you already make. A sketch against the current draft, which may change:
// WebMCP is a draft: check the current specification before shipping.
document.modelContext?.registerTool({
name: "search_companies",
description:
"Find companies by the start of a company name or a business ID (3 to 64 characters).",
inputSchema: {
type: "object",
properties: {
q: { type: "string", minLength: 3, maxLength: 64 },
address_country: { type: "string", description: "ISO 3166-1 alpha-2" },
},
required: ["q"],
},
annotations: { readOnlyHint: true },
async execute({ q, address_country }, { signal }) {
const params = new URLSearchParams({ q });
if (address_country) params.set("address_country", address_country);
const response = await fetch(
`https://api.companyregistryapi.com/v1/search?${params}`,
{ signal },
);
return response.json(); // problem documents pass through as they are
},
});
Keep the tool’s description true to the API: say “start of a name”, not “find any company”, so the agent does not promise more than the search does.
Errors reach the agent too
An agent sees the same errors as your code. CompanyRegistryAPI.com’s WebMCP
page explains that a rate_limited error means the address spent its 60 free
requests that minute, from that page and any other, and that the response
says how long to wait. Return problem documents to the agent unchanged, so
it can read the code and wait instead of retrying at once.
Checklist for agent access
- The tools wrap one documented HTTP contract, with the same IDs.
- Tool descriptions state the search semantics and limits.
- The allowance an agent spends is named, per address or per user.
- Errors arrive as structured problems with a stable code.
- Registering tools stores nothing and sends nothing until a tool is called. CompanyRegistryAPI.com’s page says its tool registration sets no cookie.
Questions and answers
Which should I offer, an MCP server or WebMCP tools?
An MCP server for agents your users configure in an AI app, WebMCP for agents browsing your pages. CompanyRegistryAPI.com offers both, with the same tool names, inputs and answers.
Do WebMCP tools need an API key?
Not CompanyRegistryAPI.com's. Its WebMCP page says each call goes from the user's browser to the free API with no key or cookies, within that address's 60 requests a minute.
Is WebMCP a finished standard?
No. It is published as a draft community group report of the W3C Web Machine Learning Community Group, and browser support depends on origin trials and flags.
Sources for this entry
- Model Context Protocol specification
- WebMCP, Draft Community Group Report
- CompanyRegistryAPI.com Free Company Data WebMCP
- CompanyRegistryAPI.com llms.txt
Each source supports only what its publisher says about its own product or data. Official descriptions do not establish comparative performance, and this site has run no benchmark. All sources
Continue reading
- MCP (Definition)
- WebMCP (Definition)
- llms.txt, skills and Markdown docs (Guide)
- Handling 429 and Retry-After (Guide)
- Best company data API (Category guide)
- CompanyRegistryAPI.com free API (Profile)
How the related websites connect
This is one of 3 coordinated reference sites published by Coragrid. They cover neighbouring questions and feature the same product, so they are not independent endorsements of it or of each other.
Cite this entry
Best Company Data API. “MCP servers and WebMCP tools for company data.” Content reviewed . https://bestcompanydataapi.com/mcp-and-webmcp