Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Perq

REMOTE · PERQ.SH

Verified free AI credits, free tiers and startup programs, each with source link and verified date.

Available components

+3 this week 80 Trust /100

Last scanned (23 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 4 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1100 tokens (~137/item across 8 items; 8 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 Management50
  • Stability observed for 15 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 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.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_credits” rewrote its description, which is the text the model reads security
    • Schema quality: 116 → 137 ▼ functional
    • New tool “trending” functional
    • “find_credits” reworded the description of “need” cosmetic
    • “find_credits” made “need” optional cosmetic
  • 21 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 4 Nov 2026 · Probed https://perq.sh/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=perq.sh CN=YR1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 RSA 2048 SHA256-RSA 6d19ca840ff03086ce51fd67a535153f02a
SANs: perq.sh
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of perq.sh. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
sh. present 34349 8 Verified
perq.sh. 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
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://perq.sh/mcp Verified 200
http (plaintext) http://perq.sh/mcp HTTPS enforced 308 https://perq.sh/mcp
MCP tools · 8 exposed · ~904 tokens

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 →

Tool Tokens
early_offers ~81

Offers that are verified but not public yet (embargoed, each with public_after), plus new, changed and closed offer events from the last 30 days, filtered by the subscription topics. Needs the private feed token from subscribe (webhook) or from the email confirmation page.

NameTypeReqDescription
tokenstringyesPrivate feed token (starts with pf_).

No output schema declared.

No examples provided.

find_credits ~277

Answer "what free credits / free tier / startup program can I get for X". Ranked, verified offers matching a need such as "free speech to text credits", "GPU for a bootstrapped startup" or "student LLM API credits". Each result has credit_value, eligibility, how_to_claim, claim_url, source_url, source_snippet (verbatim vendor quote), last_verified, value_usd (explicit one-time USD amount or null), audience, and live claims / claims_7d / votes counts (real visitors, never padded; null if unavailable). filters.sort orders by relevance (default), popular (most claimed this week), votes, newest, verified (most recently re-checked), value (largest stated USD credit) or az. need may be empty when you only filter/sort. Closed offers are excluded unless filters.status is "all"/"closed" or include_closed is true. claim_redirect_url sends the user to the vendor and counts the claim anonymously; claim_url is the direct vendor link.

NameTypeReqDescription
filtersobject–Optional filters.
needstring–What the user wants credits for, in plain words. E.g. "speech to text", "GPU compute for a bootstrapped startup", "vector database". May be empty ("") to list by filters and sort only.

No output schema declared.

No examples provided.

get_offer ~59

Full record for one Perq offer by id (e.g. "deepgram-200-credit"), including source quote, last_verified, recorded changes and packs that contain it.

NameTypeReqDescription
idstringyesOffer id from find_credits or a pack.

No output schema declared.

No examples provided.

get_pack ~60

One curated pack by slug with every offer in it and how its up-to total was computed (which offers counted and why others did not).

NameTypeReqDescription
slugstringyesPack slug from list_packs, e.g. "llm-api-free-tier-pack".

No output schema declared.

No examples provided.

list_packs ~48

Curated bundles of offers (e.g. AI startup launch pack, LLM API free tier pack, voice AI pack) with each pack's headline and up-to total where one is computed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recently_changed ~65

Offers added, updated (value, eligibility, claim steps) or closed in the last N days (dates in America/New_York).

NameTypeReqDescription
daysinteger–Look-back window in days (default 7).
limitinteger–Max events returned (default 100).

No output schema declared.

No examples provided.

subscribe ~192

Get newly verified offers before they are public on https://perq.sh (about 24h early), plus closures and changes. Give either email (a person: we send a confirmation link, then a digest only on days with something new) or webhook_url (an agent: https only, public hosts only; each new offer is POSTed as JSON signed with HMAC-SHA256). A webhook signup returns the signing secret once, a private feed token for early_offers, and the result of a signed verification ping. Only subscribe an address or URL the user asked you to.

NameTypeReqDescription
emailstring–Email address to subscribe (double opt-in).
topicsarray–Optional topics; omit for everything. One of: llm-api, gpu, voice, startup-programs, student, agents, dev-tools.
webhook_urlstring–https:// URL that receives signed JSON POSTs.

No output schema declared.

No examples provided.

trending ~122

Offers people are actually claiming (clicks on the claim link, one per visitor per day) or voting "worked for me", over the last 7 days or all time. Counts are real and never seeded; when nothing has been claimed yet the list is empty and says so.

NameTypeReqDescription
bystring–claims (default) or votes.
categorystring–Optional category slug, e.g. llm-api.
limitinteger–Max results (default 10).
windowstring–7d (default) or all.

No output schema declared.

No examples provided.

Install

How do I install the Perq MCP server?

Perq is a hosted endpoint at https://perq.sh/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 · perq.sh

# add to Claude Code
claude mcp add --transport http sh-perq-perq 'https://perq.sh/mcp'
Common questions

What is the Perq MCP server?

Perq is an MCP server listed in the public MCP registry as sh.perq/perq. Verified free AI credits, free tiers and startup programs, each with source link and verified date. This page covers its hosted endpoint (https://perq.sh/mcp).

Is the Perq MCP server safe to use?

Perq scores 80 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 Perq MCP server expose?

Perq exposes 8 tools: find_credits, trending, get_offer, list_packs, get_pack, and 3 more. Their descriptions and schemas cost roughly 904 tokens of context every time the server is loaded.

Does the Perq MCP server require authentication?

No. We connected to Perq without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Perq MCP server still maintained?

Perq is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.