C

Context

ai.everydaysecurity/context · v1.0.0 · MCP server

by ai.everydaysecurityScan grade: GoodOfficial MCP registry · source scanned

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

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is Context a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

  • MCP
  • 1 MCP server

Before you install

Sign-in
Not declared
Declared access
Not declared
License
Not declared

Check before relying on it

  • 3 medium findings from the scan. See the evidence
  • The publisher has not verified ownership on HOL.
  • No license declared in the manifest.

What is Context?

Context is a published mcp server plugin for AI coding agents in the MCP ecosystem, developed by ai.everydaysecurity and distributed through the HOL AI plugin registry. OSINT investigations with traceable evidence: domains, URLs, IPs, scams and business records.

Canonical slug
ai.everydaysecurity/context
Version
v1.0.0 · updated Oct 29, 2026

Registry snapshot

Owner verification
Not verified
Scanner
HOL plugin scanner
Security result
Needs review
Digest verified
No

Trust and security

Provenance

Plugin root
.
Source repo
https://github.com/everydaysecurity-ai/context-osint-mcp
Source commit
a83be10afa76…
Publisher verified
No
Owner verified
Not owner verified
Needs review
Security result
84
Security score
0
High findings
Provider
codex-plugin-scanner
Grade
B · Good
Version
3.24.2
cisco-mcp-scanner: skipped

Security

16/16

9 checks

Operational Security

9/17

5 checks

Best Practices

6/6

4 checks

Code Quality

10/10

2 checks

Findings

mediumoperational-securityGITHUB_ACTION_UNPINNED

.github/workflows/ci.yml references "actions/checkout@v5" instead of a full 40-character commit SHA.

Pin third-party GitHub Actions and reusable workflows to a full commit SHA.

mediumoperational-securityGITHUB_ACTION_UNPINNED

.github/workflows/publish-registry.yml references "actions/checkout@v5" instead of a full 40-character commit SHA.

Pin third-party GitHub Actions and reusable workflows to a full commit SHA.

mediumoperational-securityGITHUB_ACTION_UNPINNED

.github/workflows/tools-drift.yml references "actions/checkout@v5" instead of a full 40-character commit SHA.

Pin third-party GitHub Actions and reusable workflows to a full commit SHA.

lowoperational-securityDEPENDABOT_MISSING

Automation or dependency surfaces exist, but .github/dependabot.yml is missing.

Add Dependabot updates for GitHub Actions and dependency manifests.

Install guidance

Install in MCP

Connect the bundled MCP server shipped in the repository .mcp.json file.

MCP docs
  1. 1

    Clone the repository

    shell
  2. 2

    Register the server in your MCP client

    Claude Code reads a project .mcp.json file and asks you to approve its servers when you open the folder. Other clients keep their own MCP configuration, so copy the server entry from .mcp.json into that client. If this repository configures its server differently, follow the MCP setup the publisher documents.

  3. 3

    Verify the server

    Check the MCP server list in your client. The server declared in .mcp.json should report as connected. In Claude Code, run /mcp to see it.

Did setup work in MCP?

No setup reports for MCP yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W43, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "source": "official-mcp-registry",
  "evidenceState": "scanned_source",
  "registryName": "ai.everydaysecurity/context",
  "publishedAt": "2026-10-29T15:58:20.980572Z",
  "packages": [],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://context.everydaysecurity.ai/api/mcp"
    }
  ],
  "sourceScannedAt": "2026-10-30T19:07:34.918Z",
  "sourceScanCommit": "a83be10afa7697f8611a57bac85484706b9664e3"
}

File inventory

File inventory is unavailable for this plugin right now.

Context — Frequently asked questions

What is Context?
Context is an AI plugin in the HOL registry. OSINT investigations with traceable evidence: domains, URLs, IPs, scams and business records.
How do I install Context?
Install Context in your harness: MCP — git clone https://github.com/everydaysecurity-ai/context-osint-mcp. Full step-by-step guidance is on the HOL plugin page.
How do I install Context in MCP?
To install Context in MCP, start with git clone https://github.com/everydaysecurity-ai/context-osint-mcp. The complete step-by-step install guide for MCP is on the HOL plugin page.
Who publishes Context?
Context is published by ai.everydaysecurity and listed on HOL.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W43. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.