Arkolith/Glossary/Model Context Protocol (MCP)
AI, agents & MCP

Model Context Protocol (MCP)

Also: MCP · Model Context Protocol

What is the Model Context Protocol (MCP)?

The Model Context Protocol (MCP) is an open standard, introduced by Anthropic in late 2024, that lets AI applications connect to external tools and data through one uniform client–server interface — so any compatible model can use any MCP server.

MCP standardizes the "USB-C port" between LLMs and the outside world. Instead of every model and every data source needing a bespoke integration, an MCP server exposes tools, resources, and prompts, and any MCP client (Claude, an IDE, an agent runtime) can discover and call them the same way.

It matters because it decouples capability from model. A data provider writes one MCP server; every MCP-aware agent can immediately use it without custom glue code.

Example

Connect an MCP server to Claude and the model can call its tools — query a database, fetch a filing — without any provider-specific SDK.

Why it matters for Arkolith

Arkolith is MCP-native: the customer's own agent calls our MCP server directly, so we never run inference. MCP is the distribution channel for the whole product.

Arkolith turns this into live, sourced data your agent can query — SEC filings, insider activity, and market data behind one key, every datapoint traceable to its origin.