INDIVIDUAL MCP TOOL

developments

Dated, cited developments surfaced by your team's research runs, the runs of the one team the caller's key reads: grounded findings with a headline, category, verification state, and corroborating source count.

stonewake.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.stonewake.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for developments and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

stonewake.ai

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.stonewake-mcp]
url = "https://mcp.stonewake.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "stonewake-mcp": {
      "type": "http",
      "url": "https://mcp.stonewake.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: stonewake-mcp
Remote MCP URL: https://mcp.stonewake.ai/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": {
    "stonewake-mcp": {
      "url": "https://mcp.stonewake.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "stonewake-mcp": {
      "type": "http",
      "url": "https://mcp.stonewake.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "stonewake-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.stonewake.ai/mcp"
}

MCP Inspector

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

Related tools

portfolio_overview — Current health of the monitored portfolio: how many exposures sit in each status band (green, amber, red, insufficient, not_assessed), the active exposure count, the number of transitions in the last 30 days and how many of them are status changes (an exposure's first assessment is an addition to the book, a transition but not a change), and how many exposures have an overdue credit review.
portfolio_book — The monitored book itself: one row per exposure with the team whose book holds it (team_id, team_name), its label, register identifier, entity class (corporate, sovereign_or_public_body, bank, spv or fund, derived from register-stated facts and null when none has been derived yet), desk, current status band, score, completeness, seen_share (the weight share of applicable signals actually observed), explained_share and reachable_share (the observed share of what a connected source can serve, the figure the insufficient floor reads), the top contributing signals with their citation ids, the most recent status change, and the standing credit review (disposition, note, next review date, and whether that date has passed).
portfolio_import_preview — Preview adding a book of companies to the caller team's monitored portfolio.
entity_risk_profile — The caller team's credit-risk view of one company, by its graph node_id (the id search_companies hits carry).
search_companies — Find a company by name or identifier.
company_profile — One registry row's identity from the closed Stonewake registry of named market participants (export credit agencies, multilaterals and banks, plus the trade publications deals cite): slug, display name, full name, kind, country, aliases, and group memberships.
scoring_rubric — How scores are produced for the caller's team: the live scoring configuration (signal weights, status thresholds, evidence-coverage floor; version null means the built-in desk default is active) together with the team's stored rubric versions, newest first.
search_stonewake_docs — Search the Stonewake API documentation at docs.