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.

AI Apps That Work free tools

REMOTE · AIAPPSTHATWORK.COM

Real cost per AI result, LLM prices, switch costs, shutdown dates, A/B test sizes and judge checks.

+3 this week 75 Trust /100

Last scanned (20 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1885 tokens (~235/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 Management30
  • Stability observed for 9 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
  • Structured output schemas are declared (100% 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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 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.

  • 18 Nov 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.

  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 14 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 71

    First indexed and scored.

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 21 Nov 2026 · Probed https://aiappsthatwork.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.aiappsthatwork.com CN=YR1,O=Let's Encrypt,C=US 12 Nov 2026 10 Feb 2027 RSA 2048 SHA256-RSA 56b2535331f860505f16282af87f5cc339b
SANs: *.aiappsthatwork.com, aiappsthatwork.com
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 aiappsthatwork.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
aiappsthatwork.com. No DS 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aiappsthatwork.com/mcp Verified 200
http (plaintext) http://aiappsthatwork.com/mcp HTTPS enforced 308 https://aiappsthatwork.com/mcp
MCP tools · 8 exposed · ~1,782 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
ab_test_sample_size ~184

Returns how many results each version of a prompt or model needs before a difference in how often results work first time is statistically real (two-proportion z-test, two-sided), the total across both versions, and how many days that takes at a given daily volume.

NameTypeReqDescription
baselinePctnumberyesShare of version A's (the current prompt or model) results that work first time, percent (above 0, below 100)
confidencePctnumber–Confidence level, percent. Two-sided.
powerPctnumber–Chance of detecting a real difference of this size, percent
resultsPerDaynumber–Results per day across both versions, split evenly. Gives the number of days.
targetPctnumberyesShare of version B's results that work first time, percent (above 0, below 100)
NameTypeReqDescription
alphanumberyesFalse-positive rate, 1 minus the confidence level
baselinePctnumberyes–
days–yesNull when resultsPerDay isn't given
methodstringyes–
otherLiftsarrayyesThe same test for B at +2, +5, +10 and +15 points; null where B would pass 100%
perVersionintegeryes–
permalinkstringyesA page on this site that shows this result, for a person to open
powernumberyes–
summarystringyes–
targetPctnumberyes–
totalintegeryes–

No examples provided.

build_judge_prompt ~431

Builds a pass/fail LLM-as-a-judge prompt for one kind of AI step (make, answer, transform, extract, judge, find, predict, plan, act or learn). Returns the prompt with {{input}} and {{result}} placeholders, numbered pass conditions (the block's starter conditions unless you send your own), up to 3 pass and 3 fail examples interleaved, and a JSON or XML answer format.

NameTypeReqDescription
blockstringyesWhat the AI step does. make: creates new content from a request (an image, a post, slides, advice); answer: replies to a question that has a right answer (a support reply, a policy question, a how-to…
criteriaarray–Pass conditions, one per item. Omitted: the starter conditions for the block.
failedExamplesarray–Real results that didn't work; labelled fail in the prompt
featureDescriptionstring–Who uses the feature, what they ask for and what a good result gives them
includeReasoningboolean–Whether the judge writes a short reason before its verdict
outputFormatstring–How the judge answers
workedExamplesarray–Real results that worked first time; labelled pass in the prompt
NameTypeReqDescription
blockstringyes–
criteriaarrayyesThe pass conditions used
leftOutOfPermalinkarrayyesInputs too long for the permalink, so its page shows the prompt without them
permalinkstringyesA page on this site that shows this result, for a person to open
placeholdersarrayyes–
promptstringyesThe judge prompt. Fill {{input}} and {{result}} for each result you check.
summarystringyes–
unfilledobjectyesParts of the prompt still shown as [bracketed] placeholders

No examples provided.

judge_agreement ~222

Compares a person's verdicts with an AI judge's verdicts on the same results. Returns the agreement rate, Cohen's kappa with confidence intervals, precision and recall per verdict, the agreement of a judge that always gives the most common verdict, a trust verdict (kappa 0.6 or more with at least 80% recall on every verdict; 0.4 to 0.6 is borderline; under 30 results is too few) and the rows where the two disagree.

NameTypeReqDescription
csvstring–The same data as CSV or TSV text instead of rows: columns named human and judge (and optionally note), or the first two columns in that order.
rowsarray–One row per result. Common words are mapped onto two verdicts: worked (worked, pass, yes, true, 1, good, kept, accepted, ok) and didn't work (didn't work, fail, no, false, 0, bad, redo, retry, reject…
NameTypeReqDescription
agreementnumberyesShare of results where the judge and the person gave the same verdict
agreementCiarrayyes95% confidence interval
alwaysSameVerdict–yesThe agreement a judge would get by always giving the most common human verdict
disagreementCountintegeryes–
disagreementsarrayyesThe first 25 results where the verdicts differ
kappanumber|nullyesCohen's kappa: agreement beyond chance. Null when it is undefined.
kappaBandstringyesLandis and Koch label for kappa
kappaCi–yes–
matrixobjectyes–
nintegeryesResults compared
perVerdictarrayyes–
permalinkstringyesA page on this site that shows this result, for a person to open
skippedRowsintegeryesCSV lines without both verdicts
summarystringyes–
verdictobjectyes–
warningsarrayyesProblems with the labelled sample itself

No examples provided.

launch_checklist ~233

The 20 AI-specific launch checks for an AI app (spending caps, rate limits, server-side keys, credit charging, version tags, records of which results worked first time, real cost per result, switching models safely). Returns the checks not yet done, each with why it matters and a request for a coding agent, plus one combined request.

NameTypeReqDescription
donearray–Ids of checks already done. Ids: spend-cap, rate-limits, server-keys, capped-retries, provider-budget, every-call-charged, deduct-server-side, refund-failures, one-charge-per-request, output-metadata…
groupstring–Only checks in one group: cost (cost and abuse), charging (charging for ai use), traceability (a record of every ai result), signals (what worked, for whom, at what cost), change (switching safely)
NameTypeReqDescription
combinedPromptstringyesOne message covering every remaining check, numbered; empty when none remain
doneCountintegeryes–
groupsarrayyes–
permalinkstringyesA page on this site that shows this result, for a person to open
remainingarrayyes–
summarystringyes–
totalintegeryes–
unknownIdsarrayyesIds in done that aren't checks

No examples provided.

model_prices ~160

Looks up list prices for LLMs (USD per million input, output and cached input tokens, and context size), image models (USD per image by quality and size) and video models (USD per second by resolution), with each price's source page, the date prices were checked and any announced API shutdown.

NameTypeReqDescription
kindstring–llm for text models priced per token, image per image, video per second
limitinteger–Most models to return
querystring–A model id such as 'gpt-4o' (only exact id matches, if any), or words that must all appear in the id, name or provider, such as 'claude sonnet'. Omitted: every model.
NameTypeReqDescription
modelsarrayyes–
permalinkstringyesA page on this site that shows this result, for a person to open
pricesCheckedstringyesDate of the last full price check. Each model also has its own priceChecked and priceChanged.
totalMatchesintegeryes–

No examples provided.

model_shutdowns ~152

Lists announced API shutdown dates for AI models from OpenAI, Anthropic, Google and other providers, with days left, the suggested replacement, the source page, and links to a cost comparison and a side-by-side test of the replacement where this site has them.

NameTypeReqDescription
includePastboolean–Include shutdowns whose date has passed
querystring–A model id such as 'gpt-4o' (only exact id matches, if any), or words that must all appear in the model ids or provider, such as 'anthropic'. Omitted: every model.
todaystring–Date to count days from, YYYY-MM-DD. Omitted: today in UTC.
NameTypeReqDescription
countintegeryes–
listCheckedstringyesDate the list was last checked against the providers' deprecation pages
permalinkstringyesA page on this site that shows this result, for a person to open
shutdownsarrayyes–
todaystringyes–

No examples provided.

model_switch_cost ~173

Compares two priced LLMs on six common task shapes (support answer, invoice extraction, lead scoring, email draft, translation, search re-ranking). Returns list prices, cost per 1,000 requests on each model, the cost ratio, the break-even (how often the new model's results must work first time, relative to the current one, to cost no more per result that works) and the current model's announced shutdown.

NameTypeReqDescription
fromstringyesThe current model: an LLM id from /models.json (openai/gpt-4o), an OpenRouter id or the model's name
tostringyesThe new model: an LLM id from /models.json (openai/gpt-6-luna), an OpenRouter id or the model's name
NameTypeReqDescription
costChangestringyesThe change in cost per request across the tasks
fromobjectyes–
fromShutdown–yesThe current model's announced API shutdown, if any
notestring|nullyes–
permalinkstringyesA page on this site that shows this result, for a person to open
pricesCheckedstringyes–
summarystringyes–
switchTestUrlstring|nullyesThe browser test that runs your own prompt on both models with your own API key
tasksarrayyes–
toobjectyes–
tokenFactornumberyesTokens the new model counts for text that is 1 token on the current one, where the provider publishes it; otherwise 1

No examples provided.

real_cost_per_result ~227

Prices the AI steps behind one request from current list prices (LLM tokens, images, video seconds or a fixed amount) and returns the cost per request, the real cost per result that worked first time (cost per request divided by the worked-first-time share), the monthly spend wasted on results that didn't work, and credit-pricing numbers: margin per result and the credits per request needed to break even or reach a target margin.

NameTypeReqDescription
pricingobject–Credit pricing. Defaults: $10 for 1,000 credits, 1 credit per request, a 2.9% + $0.30 fee and a 70% target margin.
requestsPerMonthnumberyesRequests per month, try-agains included
stepsarrayyesThe AI steps behind one request, priced from /models.json. Their costs add up to the cost per request.
workedFirstTimePctnumberyesShare of results that worked first time: no try again, undo, fix, re-ask or overrule. 1 to 100.
NameTypeReqDescription
costPerRequestUsdnumberyesSum of the steps' costs for one request
creditsobjectyes–
monthlySpendUsdnumberyes–
permalinkstringyesA page on this site that shows this result, for a person to open
pricesCheckedstringyesDate the model prices were last checked
realCostPerResultUsdnumberyesCost per request divided by the worked-first-time share: what each result that worked costs, counting failed tries
requestsPerResultnumberyesRequests paid for per result that worked
stepsarrayyes–
summarystringyes–
wastedSpendPerMonthUsdnumberyesMonthly spend on results that didn't work first time

No examples provided.

Install

How do I install the AI Apps That Work free tools MCP server?

AI Apps That Work free tools is a hosted endpoint at https://aiappsthatwork.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 · aiappsthatwork.com

# add to Claude Code
claude mcp add --transport http com-aiappsthatwork-tools 'https://aiappsthatwork.com/mcp'
Common questions

What is the AI Apps That Work free tools MCP server?

AI Apps That Work free tools is an MCP server listed in the public MCP registry as com.aiappsthatwork/tools. Real cost per AI result, LLM prices, switch costs, shutdown dates, A/B test sizes and judge checks. This page covers its hosted endpoint (https://aiappsthatwork.com/mcp).

Is the AI Apps That Work free tools MCP server safe to use?

AI Apps That Work free tools scores 75 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 AI Apps That Work free tools MCP server expose?

AI Apps That Work free tools exposes 8 tools: real_cost_per_result, model_switch_cost, model_prices, model_shutdowns, ab_test_sample_size, and 3 more. Their descriptions and schemas cost roughly 1,782 tokens of context every time the server is loaded.

Does the AI Apps That Work free tools MCP server require authentication?

No. We connected to AI Apps That Work free tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AI Apps That Work free tools MCP server still maintained?

AI Apps That Work free tools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AI Apps That Work free tools MCP server?

VerifyMCP ran 13 checks on AI Apps That Work free tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.