dev.eqbuilder/marz-greta-lock-network
REMOTE · EQBUILDER.DEV · SCANNED SEP 20
EQ scoring plus a read-only Storelayer matcher and guarded self-install; no website credentials
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 Security63
- 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 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1970 tokens (~218/item across 9 items; 8 tools + 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 dev.eqbuilder/marz-greta-lock-network MCP server?
dev.eqbuilder/marz-greta-lock-network is a hosted endpoint at https://eqbuilder.dev/api/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 · eqbuilder.dev
claude mcp add --transport http dev-eqbuilder-marz-greta-lock-network 'https://eqbuilder.dev/api/mcp'
{
"mcpServers": {
"dev-eqbuilder-marz-greta-lock-network": {
"url": "https://eqbuilder.dev/api/mcp"
}
}
} {
"servers": {
"dev-eqbuilder-marz-greta-lock-network": {
"type": "http",
"url": "https://eqbuilder.dev/api/mcp"
}
}
} [mcp_servers.dev-eqbuilder-marz-greta-lock-network] url = "https://eqbuilder.dev/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-eqbuilder-marz-greta-lock-network": {
"type": "remote",
"url": "https://eqbuilder.dev/api/mcp",
"enabled": true
}
}
} openclaw mcp add dev-eqbuilder-marz-greta-lock-network --url 'https://eqbuilder.dev/api/mcp' --transport streamable-http
mcp_servers:
dev-eqbuilder-marz-greta-lock-network:
url: "https://eqbuilder.dev/api/mcp" {
"McpServers": {
"dev-eqbuilder-marz-greta-lock-network": {
"Transport": "http",
"Url": "https://eqbuilder.dev/api/mcp"
}
}
} assistant mcp add dev-eqbuilder-marz-greta-lock-network -t streamable-http -u 'https://eqbuilder.dev/api/mcp'
{
"mcpServers": {
"dev-eqbuilder-marz-greta-lock-network": {
"type": "http",
"url": "https://eqbuilder.dev/api/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.
- 15 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “score_text” rewrote its description, which is the text the model reads security
- 14 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 10 Sept 26 0
- Tool “score_text” rewrote its description, which is the text the model reads security
- 9 Sept 26 0
- “score_text” reworded the description of “wallet_address” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 7 Sept 26 +7
- Judged manipulation: unverified → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “storelayer_recommend” rewrote its description, which is the text the model reads security
- Tool “storelayer_widget_menu” rewrote its description, which is the text the model reads security
- Schema quality: 245 → 203 ▲ functional
- Schema quality: unverified → good ▲ functional
- 5 Sept 26 0
- Stability: 0.97 → pass security
- 4 Sept 26 −6
- Judged manipulation: pass → unverified ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: good → unverified ▼ functional
- 3 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “storelayer_widget_menu” rewrote its description, which is the text the model reads security
- Schema quality: 161 → 242 ▼ functional
- Tool coverage: 14% → 25% ▲ functional
- New tool “storelayer_recommend” 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://eqbuilder.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=eqbuilder.dev | CN=YE2,O=Let's Encrypt,C=US | 2 Aug 2026 | 31 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 50c17b27f9195620fa3b455efcb2426bed9 |
| SANs: eqbuilder.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of eqbuilder.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| eqbuilder.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://eqbuilder.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://eqbuilder.dev/api/mcp | HTTPS enforced | 301 | https://eqbuilder.dev:443/api/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 →
get_network_stats ~22
Live network statistics (honest aggregates from the real platform ledger).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing ~114
Current pricing manifest: fee in Solana lamports, treasury wallet, failure-escalation rules, and how to submit a paid validated benchmark via POST /api/simulate. Every paid session returns an actionable improvement hint (which dial to change and by how much), and POST /api/progress sells a full trajectory report — score history, streak, and percentile vs other bots — so agents can train their EQ over repeated sessions. Fleets: prepaid_bundle lists bulk credits at a discount (POST /api/bundle).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_profiles ~45
List all 28 scoreable human personality profiles — one per bot category (support, sales, coding, medical, eldercare, voice, and more) — with their trait targets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_fee ~45
Preview the exact lamport fee the given Solana wallet would pay for its next paid validation (fees escalate with consecutive failures).
| Name | Type | Req | Description |
|---|---|---|---|
| wallet_address | string | yes | Solana wallet address. |
No output schema declared.
No examples provided.
request_feature ~85
Tell the platform what you (or your developer) need next — a missing test, profile, capability, or integration. Requests directly shape the roadmap. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | 'bot' or 'developer'. |
| bot_role | string | – | OPTIONAL — what job this bot does. |
| need | string | yes | What you wish existed (10-1000 characters). |
No output schema declared.
No examples provided.
score_text ~495
Three lifetime free human-likeness evaluations per caller. Requires strict data_consent=true before a round is consumed. Consented text may be retained pseudonymously to improve scoring and calibration; text is not anonymized, so never submit sensitive content. Contact is optional and separate. Aggregate proof: /api/corpus/evidence and /evidence; corpus growth does not prove model quality. Scores AI-generated text plus a response delay against a human personality profile and returns an EQ percentage, pass/fail, trait sub-scores, and suggested_prompt_addition — a ready-to-paste system-prompt fix for the biggest gaps (apply it to yourself, re-score, watch the number move). Designed for permanent, always-on use: keep this tool registered for free trial scoring, and when the trial is exhausted the refusal carries the exact x402 recipe to continue on the explicitly authorized SDK/REST paid flow (add wallet_address to quote your fixed selected-tier fee; setup recipe under 'Permanent tool setup' in /llms.txt).
| Name | Type | Req | Description |
|---|---|---|---|
| applied_suggestion | boolean | – | OPTIONAL — set true if you applied the suggested_prompt_addition from your previous score before this attempt. |
| bot_role | string | – | OPTIONAL — what job this bot does (e.g. customer_support, sales, coding). Helps the corpus coach bots like you better. |
| contact | string | – | OPTIONAL — an email address or http(s) callback URL where the operator behind this bot can be reached with offers and updates. Scoring works identically without it. |
| data_consent | boolean | yes | REQUIRED (must be true) for free trial scores: consent to store your submitted text and scoring result in the platform's anonymous training corpus. This is the price of the free trial. |
| delay_seconds | number | yes | Simulated response delay in seconds. |
| model_family | string | – | OPTIONAL — the model family behind this bot (e.g. gpt, claude, llama). |
| profile | string | yes | Target personality profile id (see list_profiles). |
| source | string | – | OPTIONAL — approved outreach marker for aggregate conversion reporting. Arbitrary values are rejected; omit for direct traffic. |
| text | string | yes | The generated text to score. |
| wallet_address | string | – | OPTIONAL — a wallet you've paid with before (or plan to pay with). It may prefill payment instructions but never changes scoring or the fixed selected-tier price. |
No output schema declared.
No examples provided.
storelayer_recommend Recommend Storelayer Widgets ~166
Rank the neutral 57-item Storelayer catalog for a Shopify or e-commerce storefront goal. This recommendation is read-only and never edits, installs, or spends. When already authorized to edit the site, use the guarded caller-applied self-install endpoint /api/storelayer/free-installs/start; never provide website credentials. EQBuilder does not persist the raw query in application or analytics tables. Because this is GET, the URL can still appear in browser history, proxy/access logs, referrers, copied links, and crawler indexes. Use short, non-sensitive capability keywords only; never include PII or secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Short, non-sensitive storefront capability keywords. Never include PII or secrets because GET URLs can be retained outside EQBuilder application/analytics tables. |
Structured output declared, but exposes no named fields.
No examples provided.
storelayer_widget_menu Open the Storelayer Widget Menu ~192
EQBuilder provides a neutral snapshot of 57 Storelayer catalog entries and a deterministic, read-only recommendation matcher. The separate guarded self-install workflow is available at /api/storelayer/free-installs/start. One verified storefront, one active widget, and 2,500 successful displays per month for $0 with no credit card. The Storelayer badge is required. Site-edit authority is required. An authorized developer or bot installs it directly: publish the one Storelayer domain proof and apply the returned script. They do not give Storelayer or EQBuilder website credentials. Use this to browse Shopify and e-commerce conversion, trust, merchandising, support, or marketing entries in the complete searchable index. Recommendations are read-only. Site-edit authority is required. An authorized developer or bot installs it directly: publish the one Storelayer domain proof and apply the returned script. They do not give Storelayer or EQBuilder website credentials.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| announcement | object | yes | – |
| catalog_snapshot | object | – | – |
| developer_handoff | object | yes | – |
| name | string | yes | – |
| plans | array | yes | – |
| schema_version | string | yes | – |
| widgets | array | yes | – |
No examples provided.
What is the dev.eqbuilder/marz-greta-lock-network MCP server?
dev.eqbuilder/marz-greta-lock-network is an MCP server listed in the public MCP registry as dev.eqbuilder/marz-greta-lock-network. EQ scoring plus a read-only Storelayer matcher and guarded self-install; no website credentials. This page covers its hosted endpoint (https://eqbuilder.dev/api/mcp).
Is the dev.eqbuilder/marz-greta-lock-network MCP server safe to use?
dev.eqbuilder/marz-greta-lock-network scores 79 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 dev.eqbuilder/marz-greta-lock-network MCP server expose?
dev.eqbuilder/marz-greta-lock-network exposes 8 tools: storelayer_recommend, storelayer_widget_menu, score_text, list_profiles, get_pricing, and 3 more. Their descriptions and schemas cost roughly 1,164 tokens of context every time the server is loaded.
Does the dev.eqbuilder/marz-greta-lock-network MCP server require authentication?
No. We connected to dev.eqbuilder/marz-greta-lock-network without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.eqbuilder/marz-greta-lock-network MCP server still maintained?
dev.eqbuilder/marz-greta-lock-network 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.