Skip to content

EverythingMeetsAI MCP server

com.everythingmeetsai/archiveeverythingmeetsai.comstreamable-httpv1.0.0Scanned

AI's impact on real-world sectors: source-linked headlines in 18 sectors. Free, read-only, no text.

7 tools: 2 change things and 5 only read.

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

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

2 of these tools change something. Run those 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 Radar 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 →

What the EverythingMeetsAI MCP server can do

The EverythingMeetsAI MCP server is published by everythingmeetsai.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: changes_since and about), but cannot delete data. 5 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

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

Last scanned Oct 31, 2026, version 1.0.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.

7 tools

Changes things 2Claude Code: ask
  • aboutWhat this record is and is not, its coverage and caveats, fair-use limits, how to get a free key, and how to attribute.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 this record is and is not, its coverage and caveats, fair-use limits, how to get a free key, and how to attribute.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • changes_sinceStories we published after a timestamp, oldest first, for polling.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
    Stories we published after a timestamp, oldest first, for polling. Use next_since from the result as the next call's since. Corrections and removals are not conveyed.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • get_storyOne published story by id (from search_stories or changes_since), with every outlet that covers it and which links are paywalled.No findings

    Why it is in this group

    • The name "get_story" says "get": a word for reading.
    Description, as the server wrote it
    One published story by id (from search_stories or changes_since), with every outlet that covers it and which links are paywalled.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_outletsOutlets that cover at least one published story, with slug, name, homepage and story count; optionally within one sector.No findings

    Why it is in this group

    • The name "list_outlets" says "list": a word for reading.
    Description, as the server wrote it
    Outlets that cover at least one published story, with slug, name, homepage and story count; optionally within one sector. Use the slug in search_stories' outlet filter.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_sectorsThe sectors stories are placed in, with slug, name, what each covers, story counts (all time and last 30 days) and the span of publication dates.No findings

    Why it is in this group

    • The name "list_sectors" says "list": a word for reading.
    Description, as the server wrote it
    The sectors stories are placed in, with slug, name, what each covers, story counts (all time and last 30 days) and the span of publication dates.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_typesThe development-type vocabulary with how many stories carry each.No findings

    Why it is in this group

    • The name "list_types" says "list": a word for reading.
    Description, as the server wrote it
    The development-type vocabulary with how many stories carry each. A type with 0 has never been assigned; treat development_type as a hint, most stories have none.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • search_storiesSearch EverythingMeetsAI's record of AI's impact on real-world sectors: source-linked headlines placed in one of 18 sectors, with outlet, country, development type and time, since …No findings

    Why it is in this group

    • The name "search_stories" says "search": a word for reading.
    Description, as the server wrote it
    Search EverythingMeetsAI's record of AI's impact on real-world sectors: source-linked headlines placed in one of 18 sectors, with outlet, country, development type and time, since 24 June 2026. Filter by sector, country, outlet, development type, headline keyword and date. Returns headline, publisher link, outlet, sector and times; never article text. An empty result means no headline matched, not that nothing happened.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

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 or outbound.

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

Sign-in required, no OAuth metadata

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

Reachable
yes
HTTP status of an anonymous initialize
402
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: initialize answered HTTP 402.

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

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.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 402; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Install

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

claude mcp add --transport http archive https://everythingmeetsai.com/mcp
claude mcp add --transport http archive https://everythingmeetsai.com/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__archive__search_stories",
      "mcp__archive__get_story",
      "mcp__archive__list_sectors",
      "mcp__archive__list_outlets",
      "mcp__archive__list_types"
    ],
    "ask": [
      "mcp__archive__changes_since",
      "mcp__archive__about"
    ],
    "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 archive. Review it before you use it.

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/com.everythingmeetsai/archive/verify?hash=bdfa373d2af3674982988ac9b8cf91c062d72dd28be23aedac00b316e029172c" | jq -e '.changed == false'

Pinned hash bdfa373d2af3, from Oct 31, 2026, 09:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.everythingmeetsai/archive/changes.xml

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

Badge

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

Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.

EverythingMeetsAI MCP server: questions and answers

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

Is the EverythingMeetsAI MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 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 EverythingMeetsAI MCP server delete data?

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

Can the EverythingMeetsAI 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 EverythingMeetsAI MCP server have?

7 tools: 2 write, 5 read. changes_since, about, search_stories, get_story, list_sectors, list_outlets and list_types.

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

Its remote endpoint did not answer the last anonymous look.

Does the EverythingMeetsAI MCP server send data to outside services?

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

Has the EverythingMeetsAI MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 31, 2026.