ARKOSCOPE Public Sources MCP
OfficialRelated Servers
Alternatives to ARKOSCOPE Public Sources MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceRead-only MCP server that lets an AI agent search a catalogue of MCP servers, agent skills and open-source AI projects, with provenance: how many sources carry an entry and when it was first and last seen. Zero dependencies, single file. Remote endpoint https://anclum.com/mcp31MIT
- AlicenseBqualityBmaintenanceApache-2.0 local stdio MCP server that analyzes project structure read-only and exposes architecture checkpoints, findings, and evolution history to coding agents. Start it with npx -y @vibe-monitor/setup@latest mcp.19121 npm6Apache 2.0
- AlicenseAqualityDmaintenanceA read-only MCP server that lets AI assistants inspect local workspace files, search context, view git diffs, and fetch a fixed GitHub profile, all within a sandboxed stdio transport.5ISC
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server for Markdown, MDX, and OpenAPI docs, exposing list, search, fetch, and OpenAPI spec tools over stdio.1MIT
- FlicenseNot gradedqualityCmaintenanceReusable, read-only MCP server that exposes a repo's knowledge files (backlog docs, decisions, design notes) as MCP resources over stdio.-
- AlicenseNot gradedqualityCmaintenanceEnables people and AI agents to query local code repositories as graphs through stdio MCP tools for project listing, search, dependency tracing, impact analysis, bridge detection, node inspection, bounded code reading, and optional LSP definition/reference lookups.MIT
TDQS
Scored across 2 tools
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.
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.
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.
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.