Content Tools

everythingmeetsai.com

Provides search and retrieval tools for published AI-impact news stories, sectors, outlets, and recent updates.

1 endpoint7 known toolsFirst detected October 17, 2026Last detected October 17, 2026

ENDPOINT 1

https://everythingmeetsai.com/mcp

No auth detected

MCP server metadata

Name: everythingmeetsai
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

AI's impact on real-world sectors, as a structured record for agents: source-linked headlines placed in one of 18 sectors (healthcare, law, retail, government, defense and more), with outlet, country and time, since June 2026. No article text. Start with list_sectors for the slugs, then search_stories. Results are headlines with publisher links, never article text; fetch the link yourself if you need the story. Attribute EverythingMeetsAI.

Known tools 7

search_stories

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.

Inferred read-only

get_story

One published story by id (from search_stories or changes_since), with every outlet that covers it and which links are paywalled.

Inferred read-only

changes_since

Stories we published after a timestamp, oldest first, for polling.

Inferred read-only

list_sectors

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.

Inferred read-only

list_outlets

Outlets that cover at least one published story, with slug, name, homepage and story count; optionally within one sector.

Inferred read-only

list_types

The development-type vocabulary with how many stories carry each.

Inferred read-only

about

What this record is and is not, its coverage and caveats, fair-use limits, how to get a free key, and how to attribute.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.everythingmeetsai]
url = "https://everythingmeetsai.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "everythingmeetsai": {
      "type": "http",
      "url": "https://everythingmeetsai.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: everythingmeetsai
Remote MCP URL: https://everythingmeetsai.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "everythingmeetsai": {
      "url": "https://everythingmeetsai.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "everythingmeetsai": {
      "type": "http",
      "url": "https://everythingmeetsai.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "everythingmeetsai",
  "transport": "streamable-http",
  "url": "https://everythingmeetsai.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.