Skip to content

AsOf MCP server

is.asof/asofasof.isstreamable-httpv0.6.0Scanned

Dated, sourced facts about AI and tech companies: what was true on a day, and what changed since.

10 tools: 1 do something that can't be undone, 6 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 AsOf MCP server can do

The AsOf MCP server is published by asof.is, a domain the MCP Registry verified. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (timeline) and create or change data (6 tools: entity_state, changes_since, coverage, claim and 2 more), but cannot delete data. 3 tools only read.

1 tool can send data out of your system (timeline).

The fixed checks matched 3 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 0.6.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.

10 tools

Can't be undone 1Claude Code: ask
  • timelineAn entity's history: its dated events (releases, launches, funding, acquisitions, partnerships) and state changes (a new CEO, a new revenue figure) in chronological order, supersed…Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "timeline" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    An entity's history: its dated events (releases, launches, funding, acquisitions, partnerships) and state changes (a new CEO, a new revenue figure) in chronological order, superseded claims included, future-dated (announced) items included. Newest first when limited. Leads with headline and highlights, the main changes among the rows asked for, ranked and said as a sentence; the rows follow. Pass predicates to filter (e.g. ['released','model_release']; hf_repo_created is the day a Hugging Face repository was created, not a release date); on for one exact date, or from/to for a range; limit default 100, max 500; offset pages back (complete: false and next_offset say there is more). assertable_only keeps claims the record asserts for their own dates: a superseded CEO is assertable for the years he held the role. Each row carries its source's title: when a question names a date, answer from the rows on that date, and when several rows share a date, the title says which post each came from. Confidence ranks sources, not dates. group: true reads the entity's company group (as in entity_state): each row's entity names its record and a fact held on two records is one row (also_on). Every row carries its kind (people, money, products, models, other); kind keeps one. summary is the sentence the timeline page leads with and counts its claims by kind, over the entity's own timeline.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
Changes things 6Claude Code: ask
  • changes_sinceWhat changed since a date, at one company (entity) or across the whole record: every claim that became true, stopped being true, or was first recorded after it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What changed since a date, at one company (entity) or across the whole record: every claim that became true, stopped being true, or was first recorded after it. Leads with headline and highlights: the changes that took effect since the date, ranked (leadership, then ownership and deals, then releases; figures and repositories last) and said as a sentence, drawn from the entity's whole record when one is named. Read them first; the rows follow. Claims dated in the future (announced for a later date) are not changes yet and are left out; timeline shows them. limit default 50, max 200; offset pages through the first 900, newest first (the last page is shortened to end there). cursor pages the same feed with no cap, in the order the claims were recorded (oldest first; order: recorded in the answer): pass "" for the first page, then next_cursor from the previous answer; not with offset. assertable_only keeps claims the record asserts for their own dates. Each row carries kind (people, money, products, models or other), the same kinds /changes filters by; kind keeps one: with offset a page is that many changes of the kind and offset counts them; with cursor the filter runs on the page read, so a page can come back short. For one entity's state on two days compared per fact, use entity_diff.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • claimOne claim by id with its sources and supersession links, its three dates (valid_from, published, recorded) and the check behind it: the method and, where kept, the passage on the s…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    One claim by id with its sources and supersession links, its three dates (valid_from, published, recorded) and the check behind it: the method and, where kept, the passage on the source page that states the value.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • coverageWhat the record covers for an entity, so an empty answer can be told apart: not covered (no source reads it), unknown (covered, nothing checked yet) or covered with nothing on that…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What the record covers for an entity, so an empty answer can be told apart: not covered (no source reads it), unknown (covered, nothing checked yet) or covered with nothing on that date. sources: the official feeds that record posts on it or speak for it, its SEC filing (CIK, ticker), Hugging Face authors, Wikidata item and the status dashboard. holds: its public claims by predicate (claims, open, kind: fact, event, list or identifier). freshness: per ingest, when it last added a claim here (last_added), when one was last checked against its source (last_checked) and when reverify.py last confirmed one against Wikidata (last_verified). gaps: what the record does not cover, e.g. 'financials: none; files with the SEC as alphabet'. group: the other records of its company group and how each joined.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • entity_stateState of an entity (a company, person, product or regulator) as of a date: the claims that held on that day, with sources and confidence, such as who its CEO was or what its revenu…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description is 2,622 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...rrent value with its sources, every dated value before it and what replaced what."

      What this check looks for
    Description, as the server wrote it
    State of an entity (a company, person, product or regulator) as of a date: the claims that held on that day, with sources and confidence, such as who its CEO was or what its revenue, valuation or headquarters was. Also returns ended: the terms that closed on or before the day (a CEO who left, a seat given up), newest first, so a former role is answered too. Omit as_of for today. For a company, person, product or regulator (a model has its own lineage fields), summary is the one dated, sourced sentence its record page opens with, title its page title from the same facts, key_facts the page's fact card (each with its claim) and faq the questions the page answers: quote summary as the record's answer. By default returns the core facts (leadership, ownership, names, financials, headquarters) and skips identifiers, bulk lists and events; pass predicates to ask for specific ones (e.g. ['subsidiary','board_member','hf_repo_created']) or scope='all'. By default only claims the record asserts are returned (valid, or primary-sourced at confidence 0.7+; never flagged or marked for review); scope='all' returns everything held on the date with its status; assertable_only overrides either default. Capped by limit (default 60, max 300); offset pages. as_of is effective time: a quarter's revenue is dated at the quarter end even though it was filed weeks later. known_by answers what could have been known on a day, strictly: only claims a source had published, or AsOf had recorded, by then; a figure published later is listed under not_yet_published and the claim it replaced is returned with ended_later; a claim no source dates that AsOf recorded later is listed under publication_unknown, not counted as known. Pass known_by alone for that day, or both for 'true on as_of, as known by known_by'. Dated events (released, launched, partnership, customer, acquired, ranking_update) are not state: ask timeline for those. group: true answers for the entity's company group (the records linked by parent_id, ownership claims or an official feed that speaks for both, and their products): each row's entity names its record, a fact held on two records is one row with the other in also_on, and group.members says how each record joined. An empty answer carries empty: the reason (nothing public, nothing held on the day, or only events and lists), the entity's coverage gaps and the records group: true would add. fact_pages lists the entity's one-fact pages today (revenue, ceo, valuation, headquarters...), each with a fetch id: the current value with its sources, every dated value before it and what replaced what.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • modelsThe latest model of an AI model family (gpt, claude, gemini, llama, grok, mistral, deepseek, qwen and the others the record follows): the newest release with its date and source, t…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The latest model of an AI model family (gpt, claude, gemini, llama, grok, mistral, deepseek, qwen and the others the record follows): the newest release with its date and source, the current model of each line with the flagship marked, and the family's answer sentence. Use it for "what is the latest Claude model" or "which GPT is current". Without family: the families the record follows and the newest release across them.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
Only reads 3Show 3 read-only tools
  • entity_diffWhat changed on an entity's record between two days: its state on from against its state on to (today when omitted), compared by claim.No findings

    Why it is in this group

    • The name "entity_diff" says "diff": a word for reading.
    Description, as the server wrote it
    What changed on an entity's record between two days: its state on from against its state on to (today when omitted), compared by claim. added: facts held on to and not on from. ended: held on from, not on to, and not replaced. replaced: the same predicate with another value, the claim that held on from beside the one that holds on to (paired by the record's superseded_by pointer, when the predicate has exactly one of each and the new value begins the day the old one ends, or when the predicate has one holder at a time, such as ceo, chair, cfo or headquarters, and one holder ended while another began). unchanged counts the claims held on both days; by_predicate gives each predicate's counts; summary is the one sentence the page /record/{slug}/diff leads with: quote it. Rows carry the fields entity_state rows carry; added rows are labelled for to, ended rows for from. Posts and Hugging Face repos are counted (skipped_posts), not listed: changes_since lists them. counts, by_predicate and summary cover the whole diff; the rows are paged in the order replaced, added, ended (limit default 50, max 200; offset pages; complete: false and next_offset say there is more). group: true reads the entity's company group (as in entity_state), each row naming its record. from must be before to.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • fetchFetch a page's markdown twin by its path: /record/{slug}.md (add ?as_of=YYYY-MM-DD for a past day), /record/{slug}/{predicate}.md (a fact page: one fact's every dated value, e.g.No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    Fetch a page's markdown twin by its path: /record/{slug}.md (add ?as_of=YYYY-MM-DD for a past day), /record/{slug}/{predicate}.md (a fact page: one fact's every dated value, e.g. /record/anthropic/revenue.md; entity_state's fact_pages lists them), /record/{slug}/diff.md?from=YYYY-MM-DD&to=YYYY-MM-DD (what changed between two days, as entity_diff answers), /timelines/{slug}.md, /timelines/{slug}/{YYYY}.md (one year of a timeline), /claim/{id}.md, /day/{YYYY-MM-DD}.md, /days/{YYYY}.md, /brief/{YYYY-MM-DD}.md, /brief/week/{YYYY-MM-DD}.md, /trends/{topic}.md (add ?in=ai or ?in=tech, and ?company=<key> for one company), or a site page: /index.md, /record.md, /timelines.md, /changes.md, /days.md, /brief.md, /trends.md, /facts.md, /people.md, /models.md, /identifiers.md, /about.md, /api-docs.md, /connect.md, /compare.md, /as-of-date.md, /data.md, /privacy.md, /terms.md. A query string a page does not read is refused. A day after today or an impossible date is not a page. A page longer than 48,000 characters is cut at a line, with a note naming the tool that returns the rest.

    Annotations the server declares

    • readOnlyHint: true
    • 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 untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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:21 UTC, unchanged since Nov 20, 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
7
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://asof.is/mcp: tools/list returned 10 tools to an anonymous client, including timeline (irreversible), entity_state (write), changes_since (write), coverage (write), claim (write) and 2 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 6 to 7

Findings

Matches of fixed checks, with the text they matched.

1 warn2 info
  • The server marks "timeline" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The description is 2,622 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...rrent value with its sources, every dated value before it and what replaced what."

    What this check looks for
  • Infotrends

    The description is 2,446 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...given, as timeline rows with their tags. limit default 50, max 200; offset pages."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 7.View diff
    • Tools that change things, listed without credentials: 6 to 7
  2. Tools1 added, 7 changed.+1 added~7 changedView diff
    • Added:modelsChanges things
    • Changed:changes_sinceChanges thingsdescriptioninputSchema
    • Changed:entity_diffOnly readsinputSchema
    • Changed:entity_stateChanges thingsdescriptioninputSchema
    • Changed:fetchOnly readsdescription
    • Changed:searchOnly readsdescriptioninputSchema
    • Changed:timelineCan't be undonedescriptioninputSchema
    • Changed:trendsChanges thingsinputSchema

Install

Pinned to version 0.6.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http asof https://asof.is/mcp
claude mcp add --transport http asof https://asof.is/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__asof__search",
      "mcp__asof__entity_diff",
      "mcp__asof__fetch"
    ],
    "ask": [
      "mcp__asof__entity_state",
      "mcp__asof__changes_since",
      "mcp__asof__timeline",
      "mcp__asof__coverage",
      "mcp__asof__claim",
      "mcp__asof__trends",
      "mcp__asof__models"
    ],
    "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 asof. Review it before you use it.

Capability tags behind 1 rule
  • mcp__asof__timeline outbound

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/is.asof/asof/verify?hash=84022db0729a9fe832887f809b72b57978d8c72d6f9335ca430f009691c733ec" | jq -e '.changed == false'

Pinned hash 84022db0729a, from Nov 14, 2026, 03:18 UTC.

Watch

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

https://radar.anlyon.com/servers/is.asof/asof/changes.xml

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

Badge

Anlyon Radar badge for is.asof/asof
[![Anlyon Radar](https://radar.anlyon.com/badge/is.asof/asof.svg)](https://radar.anlyon.com/servers/is.asof/asof)

Source: MCP Registry. Synced Nov 14, 2026, 03:17 UTC.

AsOf MCP server: questions and answers

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

Is the AsOf MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 7 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AsOf MCP server delete data?

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

Can the AsOf MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: timeline.

What tools does the AsOf MCP server have?

10 tools: 1 irreversible, 6 write, 3 read. timeline, entity_state, changes_since, coverage, claim, trends, models, search and 2 more.

Does the AsOf MCP server need sign-in or OAuth?

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

Does the AsOf MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): timeline.

Has the AsOf MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.