Foundry44
REMOTE · FOUNDRY44.DEV
Search the Foundry44 library and install animated UI components for any stack.
Available components
Last scanned (7 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 2 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 Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 321 tokens (~160/item across 2 items; 2 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 Management17
- Stability observed for 5 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 2 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 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.
- 3 Nov 26 0
- Tool “get_component” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “search_components” reworded the description of “freeOnly” cosmetic
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 60
First indexed and scored.
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 5 Nov 2026 · Probed https://foundry44.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foundry44.dev | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b0ec602f50ff10670ec9a9f527ad14f2 |
| SANs: foundry44.dev, *.foundry44.dev | ||||||
| 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 foundry44.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| foundry44.dev. | 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://foundry44.dev/mcp | Verified | 200 | |
| http (plaintext) | http://foundry44.dev/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 →
get_component Install a Foundry44 component ~205
Steps to add a Foundry44 component to the user's project, for any stack (plain HTML, React with or without shadcn, other), with its markup, options and pitfalls. Follow them in the user's project. Pro components need the user's Pro key in this server's Authorization header. Getting a Pro component counts as a download and ends the buyer's 14-day refund window: call get_component only for the Pro component the user chose, never to compare.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The component's name, as search_components gives it (e.g. 'spotlight-card'). |
| settings | object | – | Optional values that differ from the defaults: an option by its name (e.g. {"duration": 800}); a colour by its CSS variable (e.g. {"--f44-spotlight-card-color": "secondary"}) with a palette role of t… |
No output schema declared.
No examples provided.
search_components Search Foundry44 components ~85
Find animated UI components in the Foundry44 library by what they do (e.g. 'text reveal on scroll', 'cursor glow'). Returns names to pass to get_component.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only this family. |
| freeOnly | boolean | – | Only free (MIT) components. |
| query | string | – | Words describing the effect, or a component's name. |
No output schema declared.
No examples provided.
How do I install the Foundry44 MCP server?
Foundry44 is a hosted endpoint at https://foundry44.dev/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 · foundry44.dev
claude mcp add --transport http dev-foundry44-components 'https://foundry44.dev/mcp'
What is the Foundry44 MCP server?
Foundry44 is an MCP server listed in the public MCP registry as dev.foundry44/components. Search the Foundry44 library and install animated UI components for any stack. This page covers its hosted endpoint (https://foundry44.dev/mcp).
Is the Foundry44 MCP server safe to use?
Foundry44 scores 62 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 Foundry44 MCP server expose?
Foundry44 exposes 2 tools: search_components, get_component. Their descriptions and schemas cost roughly 290 tokens of context every time the server is loaded.
Does the Foundry44 MCP server require authentication?
No. We connected to Foundry44 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Foundry44 MCP server still maintained?
Foundry44 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.