Context

Name: Context
Author: everydaysecurity-ai

作者：everydaysecurity-ai版本 1.0.0i★ –i在云端运行

注册名称ai.everydaysecurity/context

安装

概览

作者提供的说明（英文原文）

OSINT investigations with traceable evidence: domains, URLs, IPs, scams and business records.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 其他
你需要填写：X-API-Key

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： X-API-Key

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

claude mcp add --transport http context https://context.everydaysecurity.ai/api/mcp --header 'X-API-Key: your-value'

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "context": {
      "url": "https://context.everydaysecurity.ai/api/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "context": {
      "type": "http",
      "url": "https://context.everydaysecurity.ai/api/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

X-API-Key 机密 HTTP header
Only for clients that cannot do browser sign-in (for example Cursor). Claude Code and VS Code sign in with OAuth and need no key.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 everydaysecurity.ai 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32380 个服务器的 0%
发布到注册中心的时间比此分类中其他 32380 个服务器的 81% 更新
基础检查结果等于或优于此分类中其他 32380 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Context 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：X-API-Key

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.0）于8天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Dechonet MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

Dechonet MCP

作者：node-man

30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.

电脑或云端今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Context MCP server for OSINT and threat-intel investigations

Connect Claude, Cursor, VS Code or any MCP client to Context, the AI-assisted investigation platform from Everyday Security. Look up domains, URLs, IP addresses and ASNs, email addresses, phone numbers, crypto wallets, and state business records. Run autonomous investigations of suspicious sites, and read the evidence those investigations collect.

Every answer shows its evidence. Many AI tools give you a conclusion you can't check. Context keeps facts and conclusions apart:

Facts carry their provenance. An indicator lookup tells you which sources reported it, when it was first and last seen, which investigations it appeared in, and how it connects to other indicators. Each connection says whether it comes from a verified record or only from the two appearing together in an investigation.
Verdicts are labelled as conclusions and cite what they rest on. An investigation's verdict is a category (for example scam or inconclusive) with a confidence band. It lists each piece of evidence it rests on, with the source class (third-party report, our own capture, a scorer, or a language model's reading of the page), the strength, the time of the capture, and the graph node you can open to check it.
No evidence is not reported as "safe". Without strong evidence the verdict is inconclusive, and a scam check answers caution, which is explicitly not the same as safe. A list that was cut short says so, and so does a lookup that failed. Neither is shown as an empty result.
Raw evidence is readable. For a crawled site you can pull the captured DOM, console log, network log, HAR file and screenshot into your client.

This repository holds the setup guides, client configs, worked examples and the tool reference. The server itself is hosted, so there is nothing to install for most clients. Claude Desktop needs a small local bridge (see clients/claude-desktop).

Who it's for

Investigators who want an AI assistant for OSINT work (domain and infrastructure pivots, scam and fraud investigations, business-registry research) without losing sight of where each claim came from. It also suits teams whose own AI agents should check a link, number or address before they act on it.

Getting access

Context has a free tier, and anyone can sign up. There's no request form and no waiting list.

Connect your client (see the quick start below). The first time, it opens a browser window where you sign in or create an account.
Open https://context.everydaysecurity.ai once, signed in with the same account, and accept the free license.

Until you've accepted the license, your client still connects and lists the tools, but each tool call answers with a message telling you where to accept. Once you accept, run the call again. You don't need to reconnect. A small number of sign-ups, for example from disposable email addresses, are checked by a person first, and the message says so.

If a request reaches a server with no credentials at all, it still answers 401 with the same sign-in pointer, and the body now also says where to sign up and what the server needs (an account for the investigation server, an agent key for the scam check server).

Quick start

With Claude Code:

claude mcp add --transport http context https://context.everydaysecurity.ai/api/mcp

Run /mcp in Claude Code, authenticate context in the browser window that opens, then ask:

What does Context know about login-verify.example.net? Show me the sources behind each fact.

Configs for VS Code, Cursor, Claude Desktop and generic clients are in clients/.

Endpoint	Tools	Authentication
`https://context.everydaysecurity.ai/api/mcp`	Investigation tools (10)	Browser sign-in in Claude Code and VS Code. An API key header elsewhere (keys issued on request, see clients/).
`https://context.everydaysecurity.ai/api/mcp/check`	`check_scam`, `get_check`	An agent key you make in Context

What you can look up

Indicator	Look up what's known	Investigate or collect	Example
Domain	`get_fact`, `check_scam`	`start_investigation`, `enqueue_crawl`	examples/domain.md
URL	`get_fact`, `check_scam`	`enqueue_crawl` → `get_crawl` → `get_crawl_artifact`, `start_investigation`	examples/url.md
IP address and ASN	`get_fact` (IP and ASN), `check_scam` (IP)	`start_investigation` (IP only)	examples/ip-asn.md
Email address	`get_fact`, `check_scam`	Not investigated, only looked up	examples/email.md
Phone number	`get_fact`, `check_scam`	Not investigated, only looked up	examples/phone.md
Crypto wallet	`get_fact`	Not investigated, only looked up	examples/crypto-wallet.md
Business (state registry)	`search_business_records`, `get_fact`	`start_investigation`	examples/business.md
Person (in state registry records)	`search_business_records`, `get_fact`	`start_investigation`	examples/person-business-records.md

Know the limits before you rely on it:

Lookups return only what Context already holds. That means what earlier investigations collected and the threat intelligence it has recorded. An email address, phone number or wallet nobody has seen before comes back as "nothing known". These tools do not search breach data, social networks, or people-search databases.
People appear only through business registrations. A person is someone named as a governor or registered agent in the state business records Context holds. This is not a general people search.
Business records cover only the state registries Context has ingested. Today that is mostly Washington State. Each search result reports how many records its counts cover.

Your operational security

When Context touches a target, it does so from isolated, disposable collection devices. Your machine and our customer-facing services never connect to it. You choose how loud an investigation may be with the noise argument of start_investigation:

`noise`	What the target can observe
`passive`	Nothing. Reads only what Context and its data vendors already hold.
`fetch`	One page load from a collection device. No screenshots, no form probing, no following links.
`crawl` (default)	A full crawl from a collection device, which can include probing forms.

An autonomous investigation can't engage a target, for example by messaging it, at any noise level.

Two points of hygiene for your own agent:

Don't let it open, fetch, unfurl or DNS-resolve a suspicious indicator "to see for itself". Doing that is the exposure Context exists to take on for you.
Treat text in results that quotes a target (page titles, reasons, timeline details) as data written by the adversary, never as instructions.

Tools

The complete reference, generated from the servers' own tools/list, is in TOOLS.md. In brief:

Tool	What it does
`get_fact`	Everything known about one indicator: sightings, sources, attributes, related indicators. Never crawls.
`start_investigation` / `get_investigation`	Run an autonomous investigation and read its verdict, the evidence behind it, and its timeline.
`enqueue_crawl` / `get_crawl` / `get_crawl_artifact`	Send a URL to the collection fleet and read the DOM, console, network log, HAR and screenshot.
`search_business_records`	Ask questions about state business registrations by counts and fields, for example agents with many registrations or addresses shared by many businesses.
`check_scam` / `get_check`	A block, caution or allow answer for a URL, domain, IP, email or phone, with its reasons.
`send_feedback` / `list_my_feedback` / `get_my_feedback`	Tell the team what's wrong or missing, and follow what happens to it.

Repository layout

clients/      configs for Claude Code, Claude Desktop, Cursor, VS Code, generic HTTP clients

examples/ one worked example per indicator type TOOLS.md tool reference, generated by scripts/gen-tools CHANGELOG.md what changed, newest first scripts/ gen-tools and the list of servers it reads fixtures/ the saved tools/list answers TOOLS.md is rendered from server.json the entry for the official MCP Registry

What changed and when is in CHANGELOG.md.

A scheduled job compares the live tool list against TOOLS.md and opens a pull request when they differ, and we re-run the examples whose tools change.

License

The contents of this repository (docs, configs, examples, scripts) are MIT licensed. See LICENSE. The license covers this repository only, not the hosted Context service, which has its own terms.