Skip to content

ClientFoyer MCP server

com.clientfoyer/clientfoyerclientfoyer.comstreamable-httpv1.2.1Scanned

ClientFoyer MCP server for a freelancer client portal - projects, updates, files, invoices.

13 tools: 1 can delete or cancel things, 5 change things and 7 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

6 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 Radar 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 →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the ClientFoyer MCP server can do

The ClientFoyer MCP server is published by clientfoyer.com, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (1 tool: deletePushSubscription) and create or change data (5 tools: createProject, addStatusUpdate, uploadFile, createPushSubscription and 1 more). 7 tools only read.

1 tool reads private data (listFiles); 1 tool brings in text other people can write (readClientLink); 1 tool can send data out of your system (createPushSubscription). 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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.2.1.

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.

13 tools

Deletes or cancels 1Claude Code: deny
  • deletePushSubscriptionDelete a webhook push subscriptionNo findings

    Why it is in this group

    • The name "deletePushSubscription" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a webhook push subscription

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Changes things 5Claude Code: ask
  • addStatusUpdateAdd a status update to a project.No findings

    Why it is in this group

    • The name "addStatusUpdate" says "add": a word for a change.
    Description, as the server wrote it
    Add a status update to a project. The update is marked as posted by an agent and appears in the client's portal feed.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • createProjectCreate a new project for the authenticated freelancer.No findings

    Why it is in this group

    • The name "createProject" says "create": a word for a change.
    Description, as the server wrote it
    Create a new project for the authenticated freelancer. Returns the new project's id, title, and status. On the Free plan a project counts toward the in-progress limit unless its status is NOT_STARTED.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • createPushSubscriptionCreate a webhook push subscription.Can send data outNo findings

    Why it is in this group

    • The name "createPushSubscription" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.webhookUrl): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Create a webhook push subscription. The webhook URL must be HTTPS. The signing secret is returned once, in this response only.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • togglePushSubscriptionToggle a webhook push subscription active stateNo findings

    Why it is in this group

    • The name "togglePushSubscription" says "toggle": a word for a change.
    Description, as the server wrote it
    Toggle a webhook push subscription active state

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • uploadFileUpload a file to a project.No findings

    Why it is in this group

    • The name "uploadFile" says "upload": a word for a change.
    Description, as the server wrote it
    Upload a file to a project. File contents are sent base64-encoded; per-plan file size limits apply.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • getClientViewGet the public client portal representation for a projectNo findings

    Why it is in this group

    • The name "getClientView" says "get": a word for reading.
    Description, as the server wrote it
    Get the public client portal representation for a project

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • listFilesList files for a project with metadataReads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "listFiles" says "list" and "file": it reads files.
    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    List files for a project with metadata

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • listInvoicesList invoices for a projectNo findings

    Why it is in this group

    • The name "listInvoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices for a project

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • listProjectsList all projects for the authenticated userNo findings

    Why it is in this group

    • The name "listProjects" says "list": a word for reading.
    Description, as the server wrote it
    List all projects for the authenticated user

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • listPushSubscriptionsList active webhook subscriptions for this API keyNo findings

    Why it is in this group

    • The name "listPushSubscriptions" says "list": a word for reading.
    Description, as the server wrote it
    List active webhook subscriptions for this API key

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • listTestimonialsList testimonials for a projectNo findings

    Why it is in this group

    • The name "listTestimonials" says "list": a word for reading.
    Description, as the server wrote it
    List testimonials for a project

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

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

Reads private data1
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 out1
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__clientfoyer__createPushSubscription"
    ]
  }
}

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:23 UTC, unchanged since Nov 17, 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
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://clientfoyer.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://clientfoyer.com
Legacy HTTP+SSE transport
yes
Dynamic client registration
no
Client ID metadata documents
no
  • HighThe whole server

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

    Matched text

    https://clientfoyer.com/mcp: tools/list returned 13 tools to an anonymous client, including deletePushSubscription (destructive), createProject (write), addStatusUpdate (write), uploadFile (write), createPushSubscription (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 17, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://clientfoyer.com/.well-known/oauth-protected-resource to none
    • RFC 9728 protected resource metadata: https://clientfoyer.com/.well-known/oauth-protected-resource to https://clientfoyer.com/.well-known/oauth-protected-resource/mcp
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no
  2. Nov 10, 2026
    • WWW-Authenticate on 401: no to yes
    • resource_metadata in WWW-Authenticate: none to https://clientfoyer.com/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://clientfoyer.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://clientfoyer.com

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.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 6 (and 6 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://clientfoyer.com/.well-known/oauth-protected-resource to none
    • RFC 9728 protected resource metadata: https://clientfoyer.com/.well-known/oauth-protected-resource to https://clientfoyer.com/.well-known/oauth-protected-resource/mcp
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no
  2. Tools11 changed.~11 changedView diff
  3. PostureRemote posture changed. WWW-Authenticate on 401: no -> yes; resource_metadata in WWW-Authenticate: none -> https://clientfoyer.com/.well-known/oauth-protected-resource; RFC 9728 protected resource metadata: none -> https://clientfoyer.com/.…View diff
    • WWW-Authenticate on 401: no to yes
    • resource_metadata in WWW-Authenticate: none to https://clientfoyer.com/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: none to https://clientfoyer.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://clientfoyer.com

Install

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

claude mcp add --transport http clientfoyer https://clientfoyer.com/mcp
claude mcp add --transport http clientfoyer https://clientfoyer.com/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__clientfoyer__listProjects",
      "mcp__clientfoyer__readClientLink",
      "mcp__clientfoyer__getClientView",
      "mcp__clientfoyer__listFiles",
      "mcp__clientfoyer__listInvoices",
      "mcp__clientfoyer__listTestimonials",
      "mcp__clientfoyer__listPushSubscriptions"
    ],
    "ask": [
      "mcp__clientfoyer__createProject",
      "mcp__clientfoyer__addStatusUpdate",
      "mcp__clientfoyer__uploadFile",
      "mcp__clientfoyer__createPushSubscription",
      "mcp__clientfoyer__togglePushSubscription"
    ],
    "deny": [
      "mcp__clientfoyer__deletePushSubscription"
    ]
  }
}

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 clientfoyer. Review it before you use it.

Capability tags behind 3 rules
  • mcp__clientfoyer__readClientLink untrusted-input
  • mcp__clientfoyer__listFiles private-data
  • mcp__clientfoyer__createPushSubscription outbound

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.clientfoyer/clientfoyer/verify?hash=69dc0ff57c95475ff63e810c188b0084466949871ae67dd74afe69b1e8fb431f" | jq -e '.changed == false'

Pinned hash 69dc0ff57c95, from Nov 16, 2026, 18:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.clientfoyer/clientfoyer/changes.xml

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

Badge

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

Source: MCP Registry · repository. Synced Nov 16, 2026, 18:17 UTC.

ClientFoyer MCP server: questions and answers

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

Is the ClientFoyer MCP server safe?

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

Yes. 1 tool can delete, cancel or revoke something: deletePushSubscription.

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

13 tools: 1 destructive, 5 write, 7 read. deletePushSubscription, createProject, addStatusUpdate, uploadFile, createPushSubscription, togglePushSubscription, listProjects, readClientLink and 5 more.

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

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

Does the ClientFoyer MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): createPushSubscription.

Has the ClientFoyer MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.