MCP
Connect an MCP client to CiteArk's live research tools over Streamable HTTP.
CiteArk exposes a live MCP server at:
https://citeark.com/mcpIt supports modern MCP Streamable HTTP and the legacy stateless handshake. Public read tools require no authentication. Private reads and request_reproduction accept a CiteArk API Key in x-api-key or Authorization: Bearer; reproduction requires run permission.
Tools
| Tool | Purpose |
|---|---|
search_research | Search compact public research records with cursor pagination |
get_repository | Read one repository and opt into only the needed sections |
get_claims | Read Claims, research plans, evidence state, canonical measurements, and optional immutable Assessments |
get_runs | Filter runs by physical execution state and Assessment conclusion separately |
get_verified_runs | Legacy state=verified compatibility view; new callers should use get_runs |
get_execution_trace | Read a run with optional logs, environment, evidence, Assessments, and attestation |
get_evidence | Resolve evidence metadata and download URL |
verify_attestation | Cryptographically verify a run's signed statement |
request_reproduction | Queue an executable Claim for reproduction |
Resources
citeark://agent-api/schema— canonical JSON Schema and measurement semanticsciteark://agent-api/openapi— OpenAPI 3.1 description of the REST interface
Client configuration
Use the client's standard remote MCP server configuration and point it to https://citeark.com/mcp. For write access, configure the header without putting the key in prompts or source code:
{
"url": "https://citeark.com/mcp",
"headers": {
"x-api-key": "${CITEARK_API_KEY}"
}
}Keep the key in your client's secret or environment-variable store. Public-search-only clients should omit the header.
Clients that have a dedicated Bearer-token field can send Authorization: Bearer ${CITEARK_API_KEY} instead.
For clients without MCP support, the same data and action surface is available through the Agent API.
WebMCP
CiteArk also registers a browser-tab companion set through Chrome's experimental WebMCP API. When a compatible browser agent visits CiteArk, it can discover search_research, get_repository, get_claims, get_runs, get_verified_runs, get_execution_trace, and get_evidence directly from the page. get_runs is the canonical entry point because it does not confuse a successful execution with scientific support.
WebMCP is separate from the persistent server at /mcp: it is available only while a CiteArk tab is open. The current browser tools are read-only and deliberately use anonymous public API requests, so they cannot expose private repositories or queue reproductions. Chrome currently requires its WebMCP origin trial or the local #enable-webmcp-testing flag.
Agent API
Compact, paginated, cacheable access to CiteArk research claims, executions, measurements, and evidence.
Core Concepts
The object chain behind a research repository snapshot — Paper, Claim, Experiment, Run, Evidence, Attestation — and the rules behind the three verification rings and the License Gate.