Loudcode
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.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 3
- No findings
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →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.
{
"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.
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.
{
"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://anlyon.dev/api/v1/servers/dev.loudcode/loudcode/verify?hash=431f16954b1be175d757b33fcfb50d20450c8676ab84edfd2406fca61177b8f5" | jq -e '.changed == false'Pinned hash 431f16954b1b, from Nov 2, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/dev.loudcode/loudcode/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/dev.loudcode/loudcode)Source: MCP Registry. Synced Nov 2, 2026, 20:17 UTC.