Skip to content

PCFHub MCP server

io.github.pcfhub/pcfhubpcfhubstreamable-httpv1.0.0Scanned

Find Power Apps PCF controls, read their docs, and validate pcfhub.json manifests.

8 tools: 8 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • 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 PCFHub MCP server can do

The PCFHub MCP server is published by the GitHub account pcfhub. It has 8 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

3 tools read private data (get_component, list_doc_sections and get_doc_page); 2 tools bring in text other people can write (list_components and list_doc_sections).

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

8 tools

Only reads 8Show 8 read-only tools
  • get_componentEverything about one control by its slug: what it does, its control type, license and repository, the current release's properties, and download links for its solutions.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    Everything about one control by its slug: what it does, its control type, license and repository, the current release's properties, and download links for its solutions. Use it once search or list_components has given you a slug; use get_doc_page for installation and configuration instructions, which this does not return. An unknown slug, or a version the control never released, returns an error naming the tool to call instead. include_versions and include_related each cost an extra query, so leave them off unless you need the release history or similar controls.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • get_doc_pageRead one documentation section of a control as Markdown — installation steps, canvas or model-driven configuration, examples, limitations.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "get_doc_page" says "get" and "doc": it reads documents.
    Description, as the server wrote it
    Read one documentation section of a control as Markdown — installation steps, canvas or model-driven configuration, examples, limitations. Use list_doc_sections first for the sections that control publishes; use get_component instead for the structured property reference. Passing a version returns the documentation pinned to that release rather than the current page. A section the control does not document returns an error pointing at list_doc_sections, and the Markdown comes back without the frontmatter the site keeps.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • list_componentsBrowse the PCFHub catalog by category, tag, author, control type, host or text, paged and sorted.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Browse the PCFHub catalog by category, tag, author, control type, host or text, paged and sorted. Use it to enumerate or narrow the catalog; use search for a plain-language question about what a control should do, and get_component for one control in full. Filters take slugs, which list_taxonomy supplies. Nothing here fails on bad input: an unrecognised sort falls back to the default, and filters matching nothing return an empty page — so read `total` and `sort` from the result rather than assuming the filters applied.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • list_doc_sectionsThe documentation sections one control publishes — overview, installation, canvas, model_driven, examples, limitations and so on — each with its title and URL.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "list_doc_sections" says "list" and "doc": it reads documents.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    The documentation sections one control publishes — overview, installation, canvas, model_driven, examples, limitations and so on — each with its title and URL. Use it before get_doc_page to learn which sections that control actually has; it returns no page content, and get_component covers the property reference. A control with no documentation and a slug that does not exist return the same error on purpose, so fall back to search rather than concluding the slug is wrong.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • list_releasesThe most recent releases across every control on PCFHub, newest first: which control, which version, whether it is a prerelease, and when it shipped.No findings

    Why it is in this group

    • The name "list_releases" says "list": a word for reading.
    Description, as the server wrote it
    The most recent releases across every control on PCFHub, newest first: which control, which version, whether it is a prerelease, and when it shipped. Use it for what has changed hub-wide; for one control's own history call get_component with include_versions instead. Bounded by limit, at most 50, and not paged — there is no cursor, so it cannot walk back beyond the newest 50.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • list_taxonomyThe vocabulary list_components filters by: the category tree, the tags in use, the authors with a published control, or the hosts a control can run in, each with its slug and a cou…No findings

    Why it is in this group

    • The name "list_taxonomy" says "list": a word for reading.
    Description, as the server wrote it
    The vocabulary list_components filters by: the category tree, the tags in use, the authors with a published control, or the hosts a control can run in, each with its slug and a count. Use it to turn a name a person used into a slug; it returns no controls, so pass the slug to list_components to see them. Not paged — categories come back as a full tree and authors as a full list, while tags are capped at the 500 most used.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • validate_manifestCheck a pcfhub.json against the rules PCFHub applies when it publishes a control: the schema version, the control block (namespace, constructor, type and framework), the demo's fid…No findings

    Why it is in this group

    • The name "validate_manifest" says "validate": a word for reading.
    Description, as the server wrote it
    Check a pcfhub.json against the rules PCFHub applies when it publishes a control: the schema version, the control block (namespace, constructor, type and framework), the demo's fidelity, bundle and presets, the media files it declares, and the release artifacts it expects to find. Use it while writing or reviewing that file, before a release is tagged. An invalid manifest is an ordinary result — valid false, with errors that block publishing and warnings that do not, each carrying the JSON pointer it applies to — so read the result rather than retrying. Only an empty, unreadable or oversized manifest (over 64 KB) is an error.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true

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 outbound.

Reads private data3
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 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 20, 2026, 19:09 UTC, unchanged since Oct 22, 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
0
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

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 pcfhub https://pcfhub.dev/mcp
claude mcp add --transport http pcfhub https://pcfhub.dev/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__pcfhub__search",
      "mcp__pcfhub__list_components",
      "mcp__pcfhub__get_component",
      "mcp__pcfhub__list_doc_sections",
      "mcp__pcfhub__get_doc_page",
      "mcp__pcfhub__list_taxonomy",
      "mcp__pcfhub__list_releases",
      "mcp__pcfhub__validate_manifest"
    ],
    "ask": [],
    "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 pcfhub. Review it before you use it.

Capability tags behind 4 rules
  • mcp__pcfhub__list_components untrusted-input
  • mcp__pcfhub__get_component private-data
  • mcp__pcfhub__list_doc_sections private-data, untrusted-input
  • mcp__pcfhub__get_doc_page private-data

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/io.github.pcfhub/pcfhub/verify?hash=25b07fe60e6591faa3546477524b5f3418a09b07b611c37981ecaea2ffa7fa24" | jq -e '.changed == false'

Pinned hash 25b07fe60e65, from Nov 21, 2026, 02:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.pcfhub/pcfhub/changes.xml

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

Badge

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

Source: MCP Registry. Synced Oct 21, 2026, 18:43 UTC.

PCFHub MCP server: questions and answers

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

Is the PCFHub MCP server safe?

No scan can promise that. What its definitions show: 8 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the PCFHub MCP server delete data?

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

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

8 tools: 8 read. search, list_components, get_component, list_doc_sections, get_doc_page, list_taxonomy, list_releases and validate_manifest.

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

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

Does the PCFHub MCP server send data to outside services?

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

Has the PCFHub MCP server changed its tools?

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