Sample Serverless MCP Servers (aws-samples/sample-serverless-mcp-servers) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 12 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
2 months ago

Sample Serverless MCP Servers

Sample implementations of MCP Servers running on AWS Serverless compute

→ aws-samples/sample-serverless-mcp-servers· listed on mcp_so

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

aws-samples

Source: mcp.so

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

mcp.so

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 5 credentials: JWT_SIGNATURE_SECRET, WEBHOOK_URL_PARAM_KEY, COGNITO_CLIENT_SECRET, SESSION_SECRET_KEY, VAULT_OIDC_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAWS_LAMBDA_LOG_STREAM_NAME
configAWS_LWA_PORT
configAWS_REGION
configCOGNITO_JWKS_URL
configECS_CONTAINER_METADATA_URI_V4
🔐 secretJWT_SIGNATURE_SECRET
configMCP_SERVER_ENDPOINT
configVAULT_OIDC_JWKS_URL
configSERVER_ENDPOINT_URL
🔐 secretWEBHOOK_URL_PARAM_KEY
configSESSION_STORE_BUCKET_NAME
configAWS_LAMBDA_FUNCTION_NAME
configMCP_ENDPOINT
configAGENT_ENDPOINT_URL
configCOGNITO_SIGNIN_URL
configCOGNITO_LOGOUT_URL
configCOGNITO_WELL_KNOWN_URL
configCOGNITO_CLIENT_ID
🔐 secretCOGNITO_CLIENT_SECRET
configSTATE_S3_BUCKET_NAME
🔐 secretSESSION_SECRET_KEY
configVAULT_OIDC_CLIENT_ID
🔐 secretVAULT_OIDC_CLIENT_SECRET
configVAULT_OIDC_AUTH_URL
configVAULT_OIDC_TOKEN_URL
configVAULT_OIDC_ISSUER
configVAULT_OIDC_LOGOUT_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — ping (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ping (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ping (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

6/12 tool handlers declare input schemas (50%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 1/12 tool handlers wrap calls in try/catch (8%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/aws-samples/sample-serverless-mcp-servers)](https://m8ven.ai/mcp/aws-samples/sample-serverless-mcp-servers)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: bbe044151e7ccc02130ca8a6393be32572e475f8
code hash: a7b93ceec644e5468b4f51f3609e8f727c31521edffc02a24f76a16b27d99bc2
verified: 6/16/2026, 1:05:44 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client