Skip to content

getasof: the As Of door MCP server

io.github.allooloo/getasofallooloostreamable-httpv0.27.0Scanned

The issuer record as of any date, from the sealed vintage: signed and receipted (RCO-10060).

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the getasof: the As Of door MCP server can do

The getasof: the As Of door MCP server is published by the GitHub account allooloo. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (list_events_since).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 0.27.0.

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.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:22 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

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.27.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http getasof https://mcp.getasof.ai/mcp
claude mcp add --transport http getasof https://mcp.getasof.ai/mcp

Run 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.

.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://radar.anlyon.com/api/v1/servers/io.github.allooloo/getasof/verify?hash=8e2d6279da17c354c58c77c22a64648bd122aa84f6ba1aa94b90d91c27be6ef3" | jq -e '.changed == false'

Pinned hash 8e2d6279da17, from Nov 13, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.allooloo/getasof/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.allooloo/getasof
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.allooloo/getasof.svg)](https://radar.anlyon.com/servers/io.github.allooloo/getasof)

Source: MCP Registry · repository. Synced Nov 13, 2026, 02:17 UTC.

getasof: the As Of door MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the getasof: the As Of door MCP server safe?

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the getasof: the As Of door MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the getasof: the As Of door MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the getasof: the As Of door MCP server have?

4 tools: 4 read. get_as_of, resolve_issuer, list_events_since and list_nodes.

Does the getasof: the As Of door MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the getasof: the As Of door MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the getasof: the As Of door MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.