Skip to content

Loudcode MCP server

dev.loudcode/loudcodeloudcode.devstreamable-httpv1.0.0Scanned

Turn what you just built into build in public posts for X, in your voice. Drafts, queue, metrics.

6 tools: 5 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 5 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Loudcode MCP server can do

The Loudcode MCP server is published by loudcode.dev, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: draft_post, queue_post, post_metrics, list_ideas and 1 more), but cannot delete data. 1 tool only reads.

1 tool reads private data (list_ideas); 2 tools bring in text other people can write (list_drafts and list_ideas); 3 tools can send data out of your system (draft_post, queue_post and post_metrics). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 5Claude Code: ask
  • draft_postWrite a build in public post for X about work the user just did, in their own voice (Loudcode knows their product, tone and past posts).Can send data outNo findings

    Why it is in this group

    • The name "draft_post" says "post": a word for a change.

    What it can reach

    • outboundThe name "draft_post" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Write a build in public post for X about work the user just did, in their own voice (Loudcode knows their product, tone and past posts). Pass a concrete summary of what was built or changed in this session: features, fixes, decisions, numbers, and why it matters to users. Returns the draft (and alternatives). It is saved in Loudcode for the user to review; it is NOT posted.
  • list_ideasPost ideas Loudcode found in the user's product, numbers, posts and repo.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_ideas" says "list": a word for reading.
    • The description's first verb is "post": a word for a change.

    What it can reach

    • private-dataThe description's first sentence says "repo": it reads repositories.
    • untrusted-inputThe description's first sentence says "post" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Post ideas Loudcode found in the user's product, numbers, posts and repo. Good when they shipped nothing new this week.
  • post_metricsHow the user's recent X posts did: views, likes, replies per post and totals, best post first.Can send data outNo findings

    Why it is in this group

    • The name "post_metrics" says "post": a word for a change.

    What it can reach

    • outboundThe name "post_metrics" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    How the user's recent X posts did: views, likes, replies per post and totals, best post first.
  • queue_postQueue a Loudcode draft to post to the user's X account: at their next free posting slot, or at a specific time.Can send data outNo findings

    Why it is in this group

    • The name "queue_post" says "post": a word for a change.

    What it can reach

    • outboundThe name "queue_post" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Queue a Loudcode draft to post to the user's X account: at their next free posting slot, or at a specific time. Only do this when the user asked to queue or schedule it.
  • weekly_checkinDo the user's weekly check-in from what you know about their week, and Loudcode plans a week of posts (saved as drafts with suggested times, not posted).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Do the user's weekly check-in from what you know about their week, and Loudcode plans a week of posts (saved as drafts with suggested times, not posted). Answer each question concretely; leave one empty if you don't know.
Only reads 1Show 1 read-only tool
  • list_draftsList the user's Loudcode drafts waiting for review, and posts queued to go out, with their ids.Reads text others writeNo findings

    Why it is in this group

    • The name "list_drafts" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    List the user's Loudcode drafts waiting for review, and posts queued to go out, with their ids.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__loudcode__list_ideas"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:22 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://loudcode.dev/mcp: tools/list returned 6 tools to an anonymous client, including draft_post (write), queue_post (write), post_metrics (write), list_ideas (write), weekly_checkin (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http loudcode https://loudcode.dev/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http loudcode https://loudcode.dev/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__loudcode__list_drafts"
    ],
    "ask": [
      "mcp__loudcode__draft_post",
      "mcp__loudcode__queue_post",
      "mcp__loudcode__post_metrics",
      "mcp__loudcode__list_ideas",
      "mcp__loudcode__weekly_checkin"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as loudcode. Review it before you use it.

Capability tags behind 5 rules
  • mcp__loudcode__draft_post outbound
  • mcp__loudcode__list_drafts untrusted-input
  • mcp__loudcode__queue_post outbound
  • mcp__loudcode__post_metrics outbound
  • mcp__loudcode__list_ideas private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.loudcode/loudcode/verify?hash=431f16954b1be175d757b33fcfb50d20450c8676ab84edfd2406fca61177b8f5" | jq -e '.changed == false'

Pinned hash 431f16954b1b, from Nov 16, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.loudcode/loudcode/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.loudcode/loudcode
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.loudcode/loudcode.svg)](https://radar.anlyon.com/servers/dev.loudcode/loudcode)

Source: MCP Registry. Synced Nov 2, 2026, 20:17 UTC.

Loudcode MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Loudcode MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Loudcode MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Loudcode MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Loudcode MCP server have?

6 tools: 5 write, 1 read. draft_post, queue_post, post_metrics, list_ideas, weekly_checkin and list_drafts.

Does the Loudcode MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Loudcode MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): draft_post, queue_post and post_metrics.

Has the Loudcode MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.