getasof: the As Of door
io.github.allooloo/getasofallooloostreamable-httpv0.1.0Scanned
The issuer record as of any date, from the sealed vintage: signed and receipted (RCO-10060).
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
get_as_ofget_as_of is the issuer record as it stood on a date: an issuer by ticker, ISIN or LEI plus a date returns the signed record of that day — every field with its source and read date…No findings
Why it is in this group
- The name "get_as_of" says "get": a word for reading.
Description, as the server wrote it get_as_of is the issuer record as it stood on a date: an issuer by ticker, ISIN or LEI plus a date returns the signed record of that day — every field with its source and read date, the sealed disclosure lines of the market-year up to that date — signed by the node of the issuer's market and receipted, so a backtest can show what it read and when. Nothing is restated and nothing is filled backwards: before the record existed the answer says before_record; in a market-year not yet sealed it says not_sealed and names the earliest sealed date. Served from the Replay store under Data Vintage (sealed market-years, 2021 forward); typed errors unknown_issuer, before_record, not_sealed, not_found; every answer carries the node signature (kid) and its RCO-10060 receipt (verify_receipt at https://mcp.rco-records.ai/mcp).
Annotations the server declares
- title: Get the issuer record as of a date
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
list_events_sinceDated, URL'd disclosure events for an issuer since a date, served by the owning node's regional door.Reads text others writeNo findings
Why it is in this group
- The name "list_events_since" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it Dated, URL'd disclosure events for an issuer since a date, served by the owning node's regional door.
Annotations the server declares
- title: List disclosure events since a date
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
list_nodesEvery market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.No findings
Why it is in this group
- The name "list_nodes" says "list": a word for reading.
Description, as the server wrote it Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.
Annotations the server declares
- title: List market nodes
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
resolve_issuerFind a listed company by ticker, ISIN or LEI: the apex names the owning node and forwards to that node's regional door for the record summary.No findings
Why it is in this group
- The name "resolve_issuer" says "resolve": a word for reading.
Description, as the server wrote it Find a listed company by ticker, ISIN or LEI: the apex names the owning node and forwards to that node's regional door for the record summary.
Annotations the server declares
- title: Resolve issuer
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http getasof https://mcp.getasof.ai/mcpclaude mcp add --transport http getasof https://mcp.getasof.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__getasof__get_as_of",
"mcp__getasof__resolve_issuer",
"mcp__getasof__list_events_since",
"mcp__getasof__list_nodes"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as getasof. Review it before you use it.
Capability tags behind 1 rule
- mcp__getasof__list_events_since untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/io.github.allooloo/getasof/verify?hash=8e2d6279da17c354c58c77c22a64648bd122aa84f6ba1aa94b90d91c27be6ef3" | jq -e '.changed == false'Pinned hash 8e2d6279da17, from Nov 5, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.allooloo/getasof/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.allooloo/getasof)Source: MCP Registry · repository. Synced Nov 5, 2026, 07:17 UTC.