Skip to content

CourierPR MCP server

com.courierpr/mcpcourierpr.comstreamable-httpv1.0.0Scanned

Search and read published company press releases across six newsroom desks and twenty categories.

7 tools: 2 change things and 5 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 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 CourierPR MCP server can do

The CourierPR MCP server is published by courierpr.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: latest_releases and how_to_file), but cannot delete data. 5 tools only read.

1 tool brings in text other people can write (get_release).

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 9, 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.

7 tools

Changes things 2Claude Code: ask
  • how_to_fileWhat filing a release on CourierPR involves: what is accepted (the press code) and the links to file, for agencies and for journalists.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What filing a release on CourierPR involves: what is accepted (the press code) and the links to file, for agencies and for journalists. Use it when the user asks how to publish or distribute a press release. Returns links only; it does not file anything.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: How to publish a press release on CourierPR
  • latest_releasesThe newest published press releases, optionally within one desk or one category.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The newest published press releases, optionally within one desk or one category. Use it for 'what is new in tech', 'latest funding announcements', 'recent releases on CourierPR'. Each result is a title, company, date, short summary and a link; the full text is on the linked page. Limitation: at most 10 per call, newest first, no date filter.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Newest press releases
Only reads 5Show 5 read-only tools
  • fetchConnector-style fetch of one press release by the id from search.No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    Connector-style fetch of one press release by the id from search. Same summary as get_release.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Fetch (connector)
  • get_releaseOne published press release by slug (the last part of its URL) or by its full courierpr.com URL: title, company, category, dateline, date, the opening 120 words and a link to the f…Reads text others writeNo findings

    Why it is in this group

    • The name "get_release" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    One published press release by slug (the last part of its URL) or by its full courierpr.com URL: title, company, category, dateline, date, the opening 120 words and a link to the full release. Use it after a search or list result when the user wants more on one item. Limitation: returns a summary, not the full text; media contact details are never included and are on the page behind a human check.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: One press release
  • list_desksThe six newsroom desks and the twenty categories under them, with slugs and links.No findings

    Why it is in this group

    • The name "list_desks" says "list": a word for reading.
    Description, as the server wrote it
    The six newsroom desks and the twenty categories under them, with slugs and links. Use it to resolve a topic the user named ('tech', 'health') into a desk or category before calling latest_releases. Returns no releases.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Newsroom desks and categories
  • search_releasesFull-text search over every published press release (title and body), optionally within one category.No findings

    Why it is in this group

    • The name "search_releases" says "search": a word for reading.
    Description, as the server wrote it
    Full-text search over every published press release (title and body), optionally within one category. Use it when the user names a company, product, person or topic. Returns short summaries with links; the full text is on the linked page. Limitation: English full-text matching, at most 10 results, no date filter.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Search press releases

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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 19, 2026, 17:23 UTC, unchanged since Oct 28, 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
2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://courierpr.com/api/mcp: tools/list returned 7 tools to an anonymous client, including latest_releases (write), how_to_file (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 courierpr https://courierpr.com/api/mcp
claude mcp add --transport http courierpr https://courierpr.com/api/mcp

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__courierpr__list_desks",
      "mcp__courierpr__search_releases",
      "mcp__courierpr__get_release",
      "mcp__courierpr__search",
      "mcp__courierpr__fetch"
    ],
    "ask": [
      "mcp__courierpr__latest_releases",
      "mcp__courierpr__how_to_file"
    ],
    "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 courierpr. Review it before you use it.

Capability tags behind 1 rule
  • mcp__courierpr__get_release 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/com.courierpr/mcp/verify?hash=9d23746fc50b90f16ec064a3c3edf2f2403ffd26962b4ce598af10fd1a37dd67" | jq -e '.changed == false'

Pinned hash 9d23746fc50b, from Nov 9, 2026, 18:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.courierpr/mcp/changes.xml

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

Badge

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

Source: MCP Registry. Synced Oct 27, 2026, 20:17 UTC.

CourierPR MCP server: questions and answers

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

Is the CourierPR MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 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 CourierPR MCP server delete data?

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

Can the CourierPR 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 CourierPR MCP server have?

7 tools: 2 write, 5 read. latest_releases, how_to_file, list_desks, search_releases, get_release, search and fetch.

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

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

Does the CourierPR MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the CourierPR MCP server changed its tools?

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