MCP server · anew

anew-mcp.yml

anew ships a first-party hosted remote MCP server that answers tools/list anonymously over plain HTTP. No OAuth challenge, no session handshake, no client library — a single POST returns the real tool set with full inputSchema and outputSchema. It is the provider's primary agent interface, and the REST API is the fallback rather than the other way round.

Open endpoint → anew provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: anew Type: Hosted endpoint Transport: Host: anew.page

Endpoint

https://anew.page/mcp

Hosted endpoint · transport

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "anew": { "url": "https://anew.page/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "anew": { "command": "npx", "args": ["-y", "mcp-remote", "https://anew.page/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://anew.page/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tool quality observed · not scored

100.0%
tools with readOnly / destructive hints
100.0%
parameters described (5 total)
0
state-changing tools without destructiveHint
1907
tool-list tokens (4 tools)
0
tools over ~1,200 tokens

From an anonymous initialize + tools/list capture measured 2026-10-27; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.

Tools