Context

ai.everydaysecurityPublished by everydaysecurity.aiOfficial publisherv1.0.0Updated Oct 29, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Hosted OSINT and threat-intel server that lets an assistant look up domains, IPs, emails, phones, wallets and business records, and run evidence-backed…

What you can do
  • Look up what is known about a domain, URL, IP, ASN, email, phone, crypto wallet, business or person in registry records, with sources and sightings
  • Run autonomous investigations of suspicious sites and read the verdict, confidence band, cited evidence and timeline
  • Send a URL to a collection fleet and read back the captured DOM, console log, network log, HAR file and screenshot
  • Get a block, caution or allow answer for a URL, domain, IP, email or phone, with reasons
  • Query state business registrations by counts and fields, such as agents with many registrations or shared addresses
  • Send feedback to the team and follow up on it
When to use it
For OSINT work where each claim must be traceable: pivoting on domains and infrastructure, scam and fraud checks, and business-registry research. Also useful when an agent should vet a link, number or address before acting on it.
Requirements
Remote hosted endpoint; nothing to install for most clients (Claude Desktop needs a small local bridge). An account is required: Claude Code and VS Code sign in with OAuth in the browser, other clients use an X-API-Key header. The free license must be accepted once on the Context website before tool calls return results. The scam-check endpoint needs an agent key created in Context.
Before you install
Investigations can touch a target: the noise argument controls whether collection is passive, a single page fetch, or a full crawl that may probe forms. Treat quoted target text in results (page titles, reasons, timeline details) as adversary-written data, not instructions, and do not let your own agent fetch or resolve suspicious indicators. Lookups only return what Context already holds and are not a general people search; business records are mostly Washington State. Account sign-up and…

Installation

In SourceWeft

  1. Open Context in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.everydaysecurity%2Fcontext/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "context": {
      "type": "http",
      "url": "https://context.everydaysecurity.ai/api/mcp"
    }
  }
}

README

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.

  1. Connect your client (see the quick start below). The first time, it opens a browser window where you sign in or create an account.
  2. 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:

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

EndpointToolsAuthentication
https://context.everydaysecurity.ai/api/mcpInvestigation 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/checkcheck_scam, get_checkAn agent key you make in Context

What you can look up

IndicatorLook up what's knownInvestigate or collectExample
Domainget_fact, check_scamstart_investigation, enqueue_crawlexamples/domain.md
URLget_fact, check_scamenqueue_crawl → get_crawl → get_crawl_artifact, start_investigationexamples/url.md
IP address and ASNget_fact (IP and ASN), check_scam (IP)start_investigation (IP only)examples/ip-asn.md
Email addressget_fact, check_scamNot investigated, only looked upexamples/email.md
Phone numberget_fact, check_scamNot investigated, only looked upexamples/phone.md
Crypto walletget_factNot investigated, only looked upexamples/crypto-wallet.md
Business (state registry)search_business_records, get_factstart_investigationexamples/business.md
Person (in state registry records)search_business_records, get_factstart_investigationexamples/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:

noiseWhat the target can observe
passiveNothing. Reads only what Context and its data vendors already hold.
fetchOne 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:

ToolWhat it does
get_factEverything known about one indicator: sightings, sources, attributes, related indicators. Never crawls.
start_investigation / get_investigationRun an autonomous investigation and read its verdict, the evidence behind it, and its timeline.
enqueue_crawl / get_crawl / get_crawl_artifactSend a URL to the collection fleet and read the DOM, console, network log, HAR and screenshot.
search_business_recordsAsk questions about state business registrations by counts and fields, for example agents with many registrations or addresses shared by many businesses.
check_scam / get_checkA block, caution or allow answer for a URL, domain, IP, email or phone, with its reasons.
send_feedback / list_my_feedback / get_my_feedbackTell 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 clientsexamples/     one worked example per indicator typeTOOLS.md      tool reference, generated by scripts/gen-toolsCHANGELOG.md  what changed, newest firstscripts/      gen-tools and the list of servers it readsfixtures/     the saved tools/list answers TOOLS.md is rendered fromserver.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.

Links

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.

Source: README.md at commit 80b4cf3

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts