Skip to main content
Glama
ARKOSCOPE Public Sources MCP

ARKOSCOPE Public Sources MCP

Official
by arkoscope

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_projectsA

List projects in the bundled, dated public ARKOSCOPE registry. Optional bounded text filter. No live feed or private API access.

get_project_sourcesA

Return an exact project name, ticker or id with public source URLs and evidence levels. Unknown inputs are not guessed. Does not fetch URLs or certify safety.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
public-source-registryThe bundled public registry including dated evidence limitations. No private application data.

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

list_projects is a browse/enumerate operation with an optional text filter, while get_project_sources resolves a single exact project (by name, ticker, or id) to source URLs and evidence levels. The descriptions make the boundary explicit, including the caveat that unknown inputs are not guessed, so an agent cannot reasonably confuse them.

Naming Consistency5/5

Both names follow the same verb_noun snake_case convention (list_projects, get_project_sources). The nouns are consistent with the domain vocabulary (projects vs. project sources), making the pattern fully predictable.

Tool Count4/5

Two tools is thin, but the server's stated scope is a narrow read-only lookup over a bundled static registry, where browse + resolve is the complete workflow. No extra tools would earn their place, though the surface is small enough that any expansion would be noticeable.

Completeness4/5

For a read-only public registry, list (with filter) plus exact lookup with sources covers the core lifecycle; no create/update/delete is needed since the data is bundled and static. Minor gaps remain, such as source-centric or fuzzy search and any pagination guidance, but agents can work around these via filter-then-get.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues