io.github.RodRomer/render-mcp
REMOTE · RENDER.MAKERMARGINS.COM · SCANNED SEP 20
Hosted browser for AI agents: screenshots, post-JS DOM, console, WCAG. No install, no API key.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 993 tokens (~165/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.RodRomer/render-mcp server?
io.github.RodRomer/render-mcp is a hosted endpoint at https://render.makermargins.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 · render.makermargins.com
claude mcp add --transport http rodromer-render-mcp 'https://render.makermargins.com/mcp'
{
"mcpServers": {
"rodromer-render-mcp": {
"url": "https://render.makermargins.com/mcp"
}
}
} {
"servers": {
"rodromer-render-mcp": {
"type": "http",
"url": "https://render.makermargins.com/mcp"
}
}
} [mcp_servers.rodromer-render-mcp] url = "https://render.makermargins.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rodromer-render-mcp": {
"type": "remote",
"url": "https://render.makermargins.com/mcp",
"enabled": true
}
}
} openclaw mcp add rodromer-render-mcp --url 'https://render.makermargins.com/mcp' --transport streamable-http
mcp_servers:
rodromer-render-mcp:
url: "https://render.makermargins.com/mcp" {
"McpServers": {
"rodromer-render-mcp": {
"Transport": "http",
"Url": "https://render.makermargins.com/mcp"
}
}
} assistant mcp add rodromer-render-mcp -t streamable-http -u 'https://render.makermargins.com/mcp'
{
"mcpServers": {
"rodromer-render-mcp": {
"type": "http",
"url": "https://render.makermargins.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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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://render.makermargins.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=makermargins.com | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f13b9183621143010e721054488df331 |
| SANs: makermargins.com, render.makermargins.com, *.render.makermargins.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 render.makermargins.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| makermargins.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://render.makermargins.com/mcp | Verified | 200 | |
| http (plaintext) | http://render.makermargins.com/mcp | Inconclusive | 405 |
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 →
accessibility_audit ~215
Run a WCAG accessibility audit on a page using axe-core in a real browser, and report the violations with the elements responsible. Because it runs against a genuinely rendered page, colour-contrast and other rules that depend on layout and computed colour actually fire — these are silently skipped by audits that parse HTML without a layout engine. Use this to check a page meets WCAG before shipping.
| Name | Type | Req | Description |
|---|---|---|---|
| max_violations | number | – | Maximum violation types to report in detail. 1-50. Defaults to 20. |
| standard | string | – | Which ruleset to run. 'wcag2aa' is the usual legal benchmark but is a narrow filter — it excludes best-practice checks such as landmarks and heading order, so a page can return zero violations and st… |
| url | string | yes | The absolute URL to audit, including https:// |
No output schema declared.
No examples provided.
inspect_element ~204
Answer 'why isn't this element showing where I expect?' for a CSS selector on a live page. Returns the resolved box model, computed display/visibility/opacity/position/z-index, colours, whether the element is inside the viewport, and — crucially — whether another element is covering it. These are the values a browser computes after the full cascade and layout; they cannot be derived from reading HTML and CSS.
| Name | Type | Req | Description |
|---|---|---|---|
| height | number | – | Viewport height in pixels. 240-2000. Defaults to 800. |
| max_matches | number | – | How many matching elements to report. 1-10. Defaults to 3. |
| selector | string | yes | CSS selector for the element to inspect, for example '.buy-button' or '#header nav a' |
| url | string | yes | The absolute URL to load, including https:// |
| width | number | – | Viewport width in pixels. 320-2560. Defaults to 1280. |
No output schema declared.
No examples provided.
page_diagnostics ~169
Load a page in a real browser and report what went wrong: JavaScript console errors and warnings, network requests that failed, and the HTTP status of the page itself. Use this when a site looks broken, a deployment might have shipped a bug, or a page loads blank and you need to know why. An agent cannot see a browser's console any other way.
| Name | Type | Req | Description |
|---|---|---|---|
| height | number | – | Viewport height in pixels. 240-2000. Defaults to 800. |
| include_warnings | boolean | – | Include console warnings and info messages, not just errors. Defaults to false. |
| url | string | yes | The absolute URL to load, including https:// |
| width | number | – | Viewport width in pixels. 320-2560. Defaults to 1280. |
No output schema declared.
No examples provided.
rendered_html ~125
Fetch a page's HTML *after* JavaScript has executed. Use this when a plain HTTP fetch returns an empty shell or a loading spinner — single-page apps, sites that build their content client-side, or anything behind a framework. Returns the final DOM as HTML text.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | number | – | Truncate the returned HTML to this many characters. Defaults to 100000. |
| url | string | yes | The absolute URL to load, including https:// |
| wait_for | string | – | Optional CSS selector to wait for before capturing, for pages that load content late. |
No output schema declared.
No examples provided.
screenshot_url ~157
Take a screenshot of a web page as it actually renders in a real browser, after JavaScript has run. Use this when you need to see a page rather than read it — checking a layout, confirming a site is up and looks right, or capturing what a user would actually see. Returns a PNG image.
| Name | Type | Req | Description |
|---|---|---|---|
| full_page | boolean | – | Capture the entire scrollable page rather than just the viewport. Defaults to false. |
| height | number | – | Viewport height in pixels. 240-2000. Defaults to 800. |
| url | string | yes | The absolute URL to capture, including https:// |
| width | number | – | Viewport width in pixels. 320-2560. Defaults to 1280. |
No output schema declared.
No examples provided.
url_to_pdf ~79
Render a web page to PDF exactly as a browser would print it. Use this to archive a page, produce a document from a rendered report, or capture something for a record. Returns a PDF file.
| Name | Type | Req | Description |
|---|---|---|---|
| landscape | boolean | – | Landscape orientation. Defaults to false. |
| url | string | yes | The absolute URL to render, including https:// |
No output schema declared.
No examples provided.
What is the io.github.RodRomer/render-mcp server?
io.github.RodRomer/render-mcp is listed in the public MCP registry as io.github.RodRomer/render-mcp. Hosted browser for AI agents: screenshots, post-JS DOM, console, WCAG. No install, no API key. This page covers its hosted endpoint (https://render.makermargins.com/mcp).
Is the io.github.RodRomer/render-mcp server safe to use?
io.github.RodRomer/render-mcp scores 67 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.RodRomer/render-mcp server expose?
io.github.RodRomer/render-mcp exposes 6 tools: screenshot_url, rendered_html, page_diagnostics, accessibility_audit, inspect_element, url_to_pdf. Their descriptions and schemas cost roughly 949 tokens of context every time the server is loaded.
Does the io.github.RodRomer/render-mcp server require authentication?
No. We connected to io.github.RodRomer/render-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.RodRomer/render-mcp server still maintained?
io.github.RodRomer/render-mcp 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.