mcp

Y2 Intel MCP

MCP server for connecting Claude, Codex, and other MCP-compatible agents to Y2.

The hosted service uses OAuth and exposes twelve read-only tools with native profile, signal, and map views. The local npm package runs over stdio using an API key. Both call the Y2 API without importing Convex application internals.

Hosted connection

Add this URL as a custom remote MCP connection in a compatible assistant:

https://y2-intel-mcp.managed-services.workers.dev/mcp

Sign in to Y2, select a workspace, and approve the read permissions you need. Manage access at Y2 Settings → Connections. Membership and entitlements apply to every request; connections expire after 30 days. Native views require MCP Apps support. Other clients receive structured data and text.

The hosted service exposes connection information, profile list/detail, report list/detail, entity list/detail, signal and regional-event reads, and three native view tools. It cannot generate reports, perform writes, execute Agent Y2, or purchase anything.

The OpenAI plugin and Claude plugin contain the same hosted connection and workflow guidance. Their presence in this repository does not imply provider approval or a public directory listing. See release operations for packaging, deployment, and publication gates.

Install

npx -y @y2-intel/mcp

Required for scoped Y2 API tools:

export Y2_API_KEY=y2_...

Optional:

export Y2_API_BASE_URL=https://api.y2.dev
export Y2_DOCS_BASE_URL=https://y2.dev
export Y2_MCP_TIMEOUT_MS=60000
export Y2_MCP_MAX_RESPONSE_CHARS=40000

Agent Y2 is disabled by default. Enable it only for keys that intentionally have the agent:y2 scope:

export Y2_MCP_ENABLE_AGENT=1

Write tools are also disabled by default. Enable them only for clients and keys that should mutate Y2 profiles, projects, automations, webhooks, or subscription delivery:

export Y2_MCP_ENABLE_WRITE_TOOLS=1

Tools

• y2_list_api_operations — enumerate every operation in the published Y2 OpenAPI document (operationId, method, path). No API key required.
• y2_call_api — call any operation by operationId (or path + method); path, query, and header parameters and JSON bodies are built from the live spec. Write and Agent Y2 operations require their respective opt-in flags.
• y2_get_openapi_operation — inspect one resolved OpenAPI operation, including required scopes, parameters, and the JSON request-body schema.
• Typed tools for reports (y2_list_reports, y2_get_report, signals, graph, audio), projects, automations, webhooks, news, recaps, feeds, OSINT (events, map, CII, country briefs, aircraft, vessels, GPS jamming, cyber threats, prediction markets), intel v2 (incidents, entities, graphs, markets, FinInt, signals, CVEs, threat actors, change watermarks, knowledge retrieval), and the public x402 receipt lookup.
• Optional y2_ask_agent and y2_create_chat_completion for Agent Y2 when enabled. The chat-completion tool accepts the OpenAI-compatible request body and returns the event stream, preserving client tool calls.

Typed tools expose the published pagination cursors, response formats, expansions, and sparse fields[...] parameters where supported. Creation tools accept idempotencyKey; conditional update/delete tools accept ifMatch. With y2_call_api, use the original OpenAPI header names (Idempotency-Key, If-Match) inside parameters. Report listing retains its documented MCP cap of 5 results.

Clients

Claude Code:

claude mcp add --env Y2_API_KEY=$Y2_API_KEY --transport stdio y2 \
  -- npx -y @y2-intel/mcp

Codex:

codex mcp add y2 --env Y2_API_KEY=$Y2_API_KEY -- npx -y @y2-intel/mcp

Codex config.toml:

[mcp_servers.y2]
command = "npx"
args = ["-y", "@y2-intel/mcp"]
env_vars = ["Y2_API_KEY"]
startup_timeout_sec = 20
tool_timeout_sec = 120
default_tools_approval_mode = "prompt"

Claude Desktop JSON is in examples/claude-desktop.json. Hermes install/integration test notes are in examples/hermes.md.

Y2 API Usage

The default API root is https://api.y2.dev. The published OpenAPI document is served from https://y2.dev/api/openapi.yaml.

MCP tool	Y2 API usage	Scope
y2_get_openapi_operation	Reads the public OpenAPI document by operationId or path	none
y2_list_reports, y2_get_report, y2_get_report_signals, y2_get_report_graph, y2_get_report_text, y2_get_report_audio_text	Report listing, detail, graph, signals, and text endpoints	reports:read
y2_get_report_audio	Report audio metadata	reports:audio
y2_list_profiles	GET /api/v1/profiles	profiles:read
y2_list_news, y2_list_recaps, y2_list_feeds	News Terminal items, AI recaps, and feed metadata	news:read
y2_list_osint_*, y2_get_country_*, y2_list_aircraft, y2_list_vessels, y2_list_finint_indicators	Situation Room OSINT, country, military, cyber-threat, market, and FinInt read endpoints	osint:read
y2_list_incidents_v2, y2_get_incident_v2, y2_list_entities_v2, y2_get_entity_v2, y2_get_entity_graph_v2, y2_list_markets_v2, y2_list_finint_intel_v2, y2_list_signals_v2, y2_get_cyber_graph_v2, y2_list_cves_v2, y2_list_threat_actors_v2	Intel v2 explorer, market, FinInt, signal, and cyber endpoints	intel:explorer, intel:finint, or intel:cyber depending on endpoint
y2_list_webhooks	List webhook configurations	webhooks:manage
y2_list_projects, y2_get_project	Project listing and detail	projects:read
y2_list_automations, y2_get_automation, y2_list_automation_runs	Automation definitions and run history	automations:read
y2_list_changes_v2	Incremental change watermarks	osint:read
y2_retrieve_knowledge_v2	Global Knowledge retrieval	intel:knowledge
y2_get_x402_receipt	Public x402 receipt lookup	none
y2_create_profile, y2_update_profile, y2_patch_profile, y2_delete_profile, y2_create_webhook, y2_update_webhook, y2_delete_webhook, y2_test_webhook, y2_update_delivery	Profile, webhook, and delivery mutation endpoints	required write/manage scope plus Y2_MCP_ENABLE_WRITE_TOOLS=1
y2_create_project, y2_patch_project, y2_create_automation, y2_patch_automation, y2_run_automation	Project and Automation mutations	projects:write or automations:write plus Y2_MCP_ENABLE_WRITE_TOOLS=1
y2_ask_agent	POST /api/v1/agent-y2/chat/stream	agent:y2 plus Y2_MCP_ENABLE_AGENT=1
y2_create_chat_completion	POST /api/v1/chat/completions	agent:y2 plus Y2_MCP_ENABLE_AGENT=1

OpenAPI v1 paths are relative to https://api.y2.dev/api/v1, so both /reports and /api/v1/reports work with y2_get_openapi_operation. Agent Y2 is disabled by default because it can use entitled Y2 account actions. Write tools are disabled by default because they mutate Y2 account configuration. Set the opt-in flags only when that behavior is intended.

Credentials must never be passed as tool arguments or pasted into prompts. Give each MCP client a least-privilege Y2 API key through its environment.

Resources

• y2://docs/index
• y2://docs/full
• y2://openapi
• y2://quickstart

Development

npm ci
npm run release:check

release:check builds the package, typechecks scripts and tests, runs unit tests and the live OpenAPI contract check, performs npm pack --dry-run, and exercises tools/resources/prompts through MCP Inspector.

Check contract alignment independently:

npm run check:openapi
# Or check a previously downloaded document:
npm run check:openapi -- /path/to/openapi.yaml

This downloads only the public spec, then checks discovery, operation coverage, routing, auth requirements, scope descriptions, parameter forwarding, enums, and numeric bounds through an in-memory MCP client. All API calls are mocked; it does not require an API key or execute account actions. The check is part of CI and fails when published operations or typed parameters drift. It does not establish authenticated API acceptance or validate response payloads against the spec.

Run live API smoke tests after exporting a scoped key:

export Y2_API_KEY=y2_...
Y2_MCP_SMOKE_TOOLS=reports,news npm run smoke:live

The agent smoke path consumes Agent Y2 chat budget and should be run only with an API key that has agent:y2:

export Y2_MCP_ENABLE_AGENT=1
Y2_MCP_SMOKE_TOOLS=agent npm run smoke:live

Release

Before publishing:

1. Run npm ci && npm run release:check.
2. Confirm GitHub Actions CI passes on main.
3. Add Y2_API_KEY as a repository secret and run the Live smoke workflow with reports,news.
4. Add NPM_TOKEN as a repository secret.
5. Run the Publish workflow or publish locally with npm publish --access public --provenance.
6. Verify npm view @y2-intel/mcp version.
7. Test Claude Code, Codex, and Claude Desktop from the npm package.

The npm tarball intentionally contains only runtime output, package docs, examples, registry metadata, license, and security policy.