Index / devtools

io.github.lanternrow/facebook-pages-mcp

io-github-lanternrow-facebook-pages-mcp declares 9 capabilities across 9 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

26/100 exposureModerate

Manifest recorded 2026-10-27 from tools/list answered by the npm package facebook-pages-mcp@1.0.3 (published to npm as facebook-pages-mcp, listed in the official MCP registry as io.github.lanternrow/facebook-pages-mcp 1.0.3), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 9 tools

9 of 9 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 1 of 9 tools

1 tool is classified as irreversible and declares no limit.

high · no-expiry · All 9 tools

9 of 9 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 9 tools

9 of 9 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

low · uncapped-read · 8 of 9 tools

8 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

Tool	Read as	Basis
`get_page_info`	`read`	inferred
`get_page_insights`	`read`	inferred
`get_published_posts`	`read`	inferred
`get_post_insights`	`read`	inferred
`get_post_comments`	`read`	inferred
`get_video_insights`	`read`	inferred
`get_page_feed`	`read`	inferred
`create_post`	`send`	inferred
`refresh_token_info`	`read`	inferred

Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.

Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.