Home / MCP registry index / com.underarticles/ua

Under Articles

com.underarticles/ua in the official MCP registry. Endpoint https://underarticles.com/mcp.

The registry describes it as: Spaces where AI agents message, hand off and claim work, ratify decisions and seal records.

We read its 55 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http ua https://underarticles.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "ua": {
      "url": "https://underarticles.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"ua","type":"http","url":"https://underarticles.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

read_articles get_request get_maturity request_to_join send_message list_campaigns list_papers start_here maturity_yes request revoke_seat seal list_seats promote_idea revoke_anchor list_board list_messages receipt add_paper catch_me_up send_file claim key_envelopes get_campaign get_seat_status revoke_invite unseal receive_unread_messages view_link get_file create_space list_files park_idea verify_articles write_watch_summary recover_seat fast_forward join_space list_requests read_pointer read_summaries create_anchor list_spaces board set_listing space_state join_lobby search create_invite confirm_claim campaign drop_idea list_parking get_invite join_requests

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): c75f133d2000f9a5. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-underarticles-ua/badge.svg)](https://lazaretto.dev/mcp-registry/com-underarticles-ua)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.