VeriScope MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERISCOPE_API_KEY | No | Optional API key for activating paid access tiers. The server works without a key using the built-in 50-Canon Golden Sandbox and teaser previews. |
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 |
|---|---|
| veriscope_discover_conceptsB | Elevate colloquial questions or news metaphors into standardized canonical academic ontologies across 24 disciplines. |
| veriscope_inspect_topographyB | Retrieve axiomatic formal kernels, scholar lineages with Wikidata QIDs, and 3+ structured dialectical disputes to prevent shallow syntheses. |
| veriscope_locate_evidenceB | Locate fair-use verbatim excerpts (<=300 chars) with exact chapter coordinates, 64-bit SHA-256 hash, and Ed25519 cryptographic receipt. |
| veriscope_verify_attestationC | Mathematically verify the Ed25519 cryptographic receipt of an academic quote to guarantee zero-hallucination and text integrity. |
| veriscope_probe_radarB | Probe matrix coverage, discipline distribution, and available conceptual nodes across all 24 academic disciplines. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool maps to a distinct stage in the evidence-verification workflow: concept discovery, contextual/topographical retrieval, verbatim evidence location, cryptographic receipt verification, and coverage probing. The only surface overlap is that discover_concepts and probe_radar both mention disciplines, but their descriptions clearly separate query-to-ontology transformation from inventory/coverage statistics.
All five tools use the same veriscope_ prefix followed by a verb_noun pattern: discover_concepts, inspect_topography, locate_evidence, verify_attestation, probe_radar. The convention is predictable and consistent across the entire tool set.
Five tools are well-scoped for this server's purpose and each earns its place in the workflow. There are no redundant tools, and the set is neither too thin nor overloaded.
The surface covers the core pipeline from concept discovery through evidence location and cryptographic verification, plus coverage probing. Minor optional gaps exist, such as batch verification or richer source/citation retrieval, but these are not critical dead ends for the stated anti-hallucination purpose.