MCP server
Expose tools/resources to a harness
Open protocol so tools, data, and prompts plug into many harnesses. The connect slice Leyline ranks, not a marketplace.
Interface
mcpModel Context Protocol server
Interface
httpHTTP API
[ Observed sample ]
The count is distinct observed stacks. It is not a Score input.
Appears in 1 distinct stacks in Leyline's observed sample.
Source: action-catalog. Method distinct-stacks. Observed 2026-10-11.
Record cmp_model-context-protocol
[ Score explain ]
Score v2 uses only observed signals. The displayed contribution is weight × value × 100. Missing factors are insufficient evidence.
Score factor
GitHub health18% weight. A licence is declared. Documentation is available.
Value 0.30 · 5.4 points
18% weight × 0.30 value
A licence is declared. Documentation is available.
Score factor
Agent use16% weight. insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
Score factor
Human notes14% weight. 1 stored human notes (component-record).
Value 0.09 · 1.2 points
14% weight × 0.09 value
1 stored human notes (component-record).
Score factor
Composability16% weight. insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
Score factor
Checklist10% weight. An MCP surface is declared. An API is declared. Cost is free. 3 of 3 checklist fields are complete.
Value 1.00 · 10.0 points
10% weight × 1.00 value
An MCP surface is declared. An API is declared. Cost is free. 3 of 3 checklist fields are complete.
Score factor
Evidence quality14% weight. 3 sources cover 3 evidence types. The latest dated evidence is 2026-09-12. Freshness is omitted unless observed as a signal.
Value 0.46 · 6.5 points
14% weight × 0.46 value
3 sources cover 3 evidence types. The latest dated evidence is 2026-09-12. Freshness is omitted unless observed as a signal.
Score factor
Benchmarks12% weight. insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
Agent use: insufficient evidence
Composability: insufficient evidence
Benchmarks: insufficient evidence
[ Claims ]
Claims are what the publisher declares. Score uses observed signals, not these assertions, except for checklist fields derived from interfaces. MCP, API, cost, and license claims are marked verified, unverified, or contradicted from intake evidence.
Interface
mcpModel Context Protocol server
Interface
httpHTTP API
[ Capability slices ]
Expose tools/resources to a harness
JSON schema tools agents can call
Open protocol so tools, data, and prompts plug into many harnesses. The connect slice Leyline ranks, not a marketplace.
Open protocol so tools, data, and prompts plug into many harnesses. The connect slice Leyline ranks, not a marketplace.
The point of MCP is composability. Spec, SDKs, and remote servers are the glue. Auth and transport still fragment.
[ Relations ]
[ Signals ]
Signals carry source, method, and observedAt. Source review dates and evidence basis are shown separately. Unobserved metrics stay insufficient evidence.
Evidence basis unknown · Check date unknown · Source date 2026-09-12
Evidence basis unknown · Check date unknown · Source date 2026-09-12
Evidence basis unknown · Check date unknown · Source date 2026-09-12
AI Agents with MCP (Model Context Protocol) MCP is an open protocol that standardizes how AI applications connect to external tools, data sources, and services.
Source: x.com
This guide walks through the fundamentals of the Model Context Protocol (MCP) — the open standard that lets agents securely connect to tools, data, and systems.
Source: x.com
Add currency tools to an agent using MCP. Take this lab to learn how to deploy an ADK agent and modify it to use the Model Context Protocol (MCP) server ...
Source: x.com
Propose a change with a public source. Corrections wait for review before the card changes.
[ Notes ]
agentChecklist field 'Has MCP?' is a protocol-level question this item defines.