Loading ToolBench

Reading the current corpus…

postcard-examples MCP server · F · ToolBench

← Browse

postcard-examples

github.com/PostcardBot/postcard-examples

Example scripts and servers for integrating with the Postcard.bot API to send physical postcards

2026-07-28+8 tools

33/100

Definition Quality41

Protocol Readiness0

Supportability41

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

This is an examples repository, not a production MCP server. No MCP server implementation is present in the source code. The repository contains Node.js and Python example scripts that call the Postcard.bot API directly, plus Express/Flask webhook receivers. Tool definitions are inferred from the provided metadata, not from actual MCP tool registration code. Schemas are present but descriptions are minimal (10-50 chars, well below the 50-200 char baseline for LLM-optimized tools). No error handling guidance, no parameter validation, no security patterns. The webhook handlers are standalone HTTP servers, not MCP tools.

Tools (8)

bulk_sendwriteauth47/100

Send postcards to multiple recipients via the Postcard.bot bulk API from a CSV file

bulk_send_pythonwriteauth47/100

Send postcards to multiple recipients via the Postcard.bot bulk API from a CSV file

check_statusread onlyauth50/100

Check the status of a postcard or bulk job

check_status_pythonread onlyauth50/100

Check the status of a postcard or bulk job

handle_webhookread onlyauthsource verified48/100

Receive and verify Postcard.bot webhook events with HMAC-SHA256 signature verification

handle_webhook_pythonread onlyauth48/100

Receive and verify Postcard.bot webhook events with HMAC-SHA256 signature verification

send_postcardwriteauth50/100

Send a single postcard via the Postcard.bot API

send_postcard_python

Issues (5)

CRITICALtool ↗

Not an MCP server implementation. Repository contains example scripts and webhook servers, not an MCP tool server with proper tool registration, capabilities negotiation, or protocol compliance.

send_postcardbulk_sendcheck_statushandle_webhooksend_postcard_pythonbulk_send_pythoncheck_status_pythonhandle_webhook_python

HIGHtool-description ↗

Descriptions are too short (10-50 chars vs. baseline 50-200 chars). 'Send a single postcard via the Postcard.bot API' lacks context on when to use this vs. bulk_send, what happens on retry, or what the response contains.

send_postcardbulk_sendcheck_statushandle_webhook

HIGHtool ↗

Duplicate tools across languages (send_postcard vs. send_postcard_python, etc.). LLMs will waste reasoning cycles deciding between functionally identical tools. Consolidate into a single canonical tool per operation.

send_postcardsend_postcard_python

Recommendations

Implement this as a proper MCP server using the MCP SDK (Node.js or Python). Register tools via the MCP protocol with capabilities negotiation, not as standalone scripts.
Expand tool descriptions to 50-200 chars. Example: 'send_postcard: Send a single postcard to a recipient. Use this for one-off mailings; use bulk_send for multiple recipients. Returns postcard_id for status tracking. Requires valid address and image URL.'
Remove duplicate language-specific tools. Implement a single send_postcard tool in the MCP server; the implementation can call Node.js or Python internally.
Add error handling guidance to descriptions. E.g., 'Returns error if address is incomplete or image URL is unreachable. Retry with corrected address or check image URL accessibility.'
Document the CSV format for bulk_send: required columns (name, address_line1, city, state, zip, country), max rows, encoding. Add a csv_format parameter or enum to specify dialect.

Score history

Overall score trend

First recorded score · v2 rubric

33/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	33	2026-07-28+	v2