io.github.paperandbeyond23-gif/propzapi
REMOTE · API.PROPZAPI.COM · SCANNED SEP 20
Render-and-verify API: HTML/CSS to image or PDF, screenshot any URL, confirm the text rendered.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 342 tokens (~114/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.paperandbeyond23-gif/propzapi MCP server?
io.github.paperandbeyond23-gif/propzapi is a hosted endpoint at https://api.propzapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.propzapi.com
claude mcp add --transport http paperandbeyond23-gif-propzapi 'https://api.propzapi.com/mcp'
{
"mcpServers": {
"paperandbeyond23-gif-propzapi": {
"url": "https://api.propzapi.com/mcp"
}
}
} {
"servers": {
"paperandbeyond23-gif-propzapi": {
"type": "http",
"url": "https://api.propzapi.com/mcp"
}
}
} [mcp_servers.paperandbeyond23-gif-propzapi] url = "https://api.propzapi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"paperandbeyond23-gif-propzapi": {
"type": "remote",
"url": "https://api.propzapi.com/mcp",
"enabled": true
}
}
} openclaw mcp add paperandbeyond23-gif-propzapi --url 'https://api.propzapi.com/mcp' --transport streamable-http
mcp_servers:
paperandbeyond23-gif-propzapi:
url: "https://api.propzapi.com/mcp" {
"McpServers": {
"paperandbeyond23-gif-propzapi": {
"Transport": "http",
"Url": "https://api.propzapi.com/mcp"
}
}
} assistant mcp add paperandbeyond23-gif-propzapi -t streamable-http -u 'https://api.propzapi.com/mcp'
{
"mcpServers": {
"paperandbeyond23-gif-propzapi": {
"type": "http",
"url": "https://api.propzapi.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Sept 26 +14
- Stability: fail → pass ▲ security
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Schema quality: 74 → 88 ▼ functional
- Tool coverage: 50% → 56% ▲ functional
- Schema quality: good → fair functional
- “generate_image” added an optional parameter “verify” cosmetic
- 2 Aug 26 0
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “get_books” was removed ▼ security
- Tool “get_events” was removed ▼ security
- Tool “get_odds” was removed ▼ security
- Tool “get_props” was removed ▼ security
- Schema quality: 64 → 74 ▼ functional
- Tool coverage: 38% → 50% ▲ functional
- Schema quality: fair → good functional
- New tool “generate_image” functional
- New tool “list_templates” functional
- New tool “screenshot_url” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.propzapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.propzapi.com | CN=WE1,O=Google Trust Services,C=US | 2 Aug 2026 | 31 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 91e9af57a53e39b13019b6c30e179c5 |
| SANs: api.propzapi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.propzapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| propzapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.propzapi.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.propzapi.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'self'; img-src 'self' https: data:; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; script-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; worker-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Protected resource metadata
| Document | https://api.propzapi.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.propzapi.com/mcp |
| Authorisation server | https://api.propzapi.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.propzapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.propzapi.com/mcp | HTTPS enforced | 301 | https://api.propzapi.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
generate_image ~202
Render an on-brand image from a template and your data, and return the image. Use list_templates first to see template ids and their variables. 1 credit per image; cost returned in _meta.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| modifications | object | – | variable -> value overrides, e.g. {"title":"...","accent":"#b45cff"}. |
| receipt | boolean | – | Return a render receipt: image_sha256, the text that actually rendered, per-string checks + misses, viewport, and timing. Lets you trust the render without looking at the pixels. |
| template | string | yes | Template id from list_templates: a built-in (e.g. og-article) or one of your own tpl_... ids. |
| verify | array | – | Strings that must render as visible text. The result reports whether each one landed (found and not clipped) — use it to confirm the exact values you passed made it into the image. |
No output schema declared.
No examples provided.
list_templates ~24
List the image templates you can render, with the variables each accepts. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
screenshot_url ~116
Screenshot any public web page and return the image. 1 credit; cost in _meta.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| full_page | boolean | – | Capture the whole scrollable page (default false = just the viewport). |
| height | integer | – | – |
| receipt | boolean | – | Return a render receipt: image_sha256, extracted page text, viewport and timing, so you can trust the capture without inspecting pixels. |
| url | string | yes | Public http(s) URL to capture. |
| width | integer | – | – |
No output schema declared.
No examples provided.
What is the io.github.paperandbeyond23-gif/propzapi MCP server?
io.github.paperandbeyond23-gif/propzapi is an MCP server listed in the public MCP registry as io.github.paperandbeyond23-gif/propzapi. Render-and-verify API: HTML/CSS to image or PDF, screenshot any URL, confirm the text rendered. This page covers its hosted endpoint (https://api.propzapi.com/mcp).
Is the io.github.paperandbeyond23-gif/propzapi MCP server safe to use?
io.github.paperandbeyond23-gif/propzapi scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.paperandbeyond23-gif/propzapi MCP server expose?
io.github.paperandbeyond23-gif/propzapi exposes 3 tools: list_templates, generate_image, screenshot_url. Their descriptions and schemas cost roughly 342 tokens of context every time the server is loaded.
Does the io.github.paperandbeyond23-gif/propzapi MCP server require authentication?
Yes. io.github.paperandbeyond23-gif/propzapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.paperandbeyond23-gif/propzapi MCP server still maintained?
io.github.paperandbeyond23-gif/propzapi is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.