Schema | VerifyAPI MCP Server

VerifyAPI MCP Server

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`VERIFYAPI_API_KEY`	No	Your VerifyAPI key (`csk_live_...`). Optional; if unset, the free trial is used (limited to 3 calls per IP per 24h). Get one free at https://verify-api.dev/signup.
`VERIFYAPI_BASE_URL`	No	Override the API base URL. Useful for self-hosting or testing.	https://api.verify-api.dev

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
verify_claimA	Fact-check a single factual claim against live web sources. Returns one of `supported`, `refuted`, `insufficient_evidence`, or `out_of_scope`, with confidence, source_url, published_date, and a verbatim exact_quote from that source. Every response is signed with an Ed25519 receipt (verifiable at https://api.verify-api.dev/.well-known/jwks.json). Pricing (see /v1/pricing): $0.02 base per supported/refuted verdict; recent tier (<24h old cache) 2x; fresh tier (cache bypassed, guaranteed live) 5x. insufficient_evidence, out_of_scope, malformed, and cache hits within your account are free. Use `freshness="cached"` (default) for maximum savings; `freshness="fresh"` when you need a guaranteed-current answer (breaking news, live standings, latest release); set `max_age_seconds` for HTTP Cache-Control-style bounded staleness. Running without an API key uses the FREE TRIAL (3 calls per IP per 24h, cached tier only, still returns signed receipts). Set VERIFYAPI_API_KEY in the mcpServers env block to remove the limit and unlock the recent/fresh tiers. Get a key at https://verify-api.dev/signup (no credit card). Use this before committing to any factual claim you are not sure about — dates, statistics, prices, attributions, event outcomes.

verify_claimA

Fact-check a single factual claim against live web sources. Returns one of supported, refuted, insufficient_evidence, or out_of_scope, with confidence, source_url, published_date, and a verbatim exact_quote from that source. Every response is signed with an Ed25519 receipt (verifiable at https://api.verify-api.dev/.well-known/jwks.json).

Pricing (see /v1/pricing): $0.02 base per supported/refuted verdict; recent tier (<24h old cache) 2x; fresh tier (cache bypassed, guaranteed live) 5x. insufficient_evidence, out_of_scope, malformed, and cache hits within your account are free. Use freshness="cached" (default) for maximum savings; freshness="fresh" when you need a guaranteed-current answer (breaking news, live standings, latest release); set max_age_seconds for HTTP Cache-Control-style bounded staleness.

Running without an API key uses the FREE TRIAL (3 calls per IP per 24h, cached tier only, still returns signed receipts). Set VERIFYAPI_API_KEY in the mcpServers env block to remove the limit and unlock the recent/fresh tiers. Get a key at https://verify-api.dev/signup (no credit card).

Use this before committing to any factual claim you are not sure about — dates, statistics, prices, attributions, event outcomes.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.7/5.0

Scored 2026-09-19 03:50 across 1 tool

Disambiguation5/5

With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly and uniquely defined, so an agent can unambiguously select it.

Naming Consistency5/5

The lone tool name `verify_claim` follows a clear verb_noun pattern. With only one tool, naming is perfectly consistent and predictable.

Tool Count4/5

The server exposes exactly one tool, which is below the typical 3-15 range but not trivial. The tool is substantial and directly serves the server's narrow fact-checking purpose, so the low count is reasonable, though slightly thin.

Completeness5/5

The domain is fact-checking a single claim, and the tool covers that end-to-end: it accepts a claim, returns a verdict with confidence, source, date, exact quote, and a signed receipt, and offers freshness controls. There are no obvious missing operations for this stated purpose.

Maintenance

ActivitySlowing

ResponsivenessNo issues