avasfood-mcp (Rayyan011/avasfood-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 21 tools. No publisher has claimed this listing.

C
Caution
74/100

avasfood-mcp

A standard Python MCP server for AVAS Food: browse menus, build and quote carts, complete bank-transfer ordering with explicit confirmation, track deliveries, and analyze delivery spending.

Caution. Specific findings reduced this grade. They are listed on the page. 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

Rayyan011

Source: Glama

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 →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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 1 credential: AVAS_ACCESS_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes21 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_client_metadata

Return verified AVAS client/API metadata and MCP safety mode.

list_restaurants

List AVAS restaurants in a Maldives delivery zone; optionally filter by name.

get_restaurant

Get public details for one AVAS restaurant by merchant ID.

search_menu_items

Search public AVAS menu items across restaurants by name or description.

account_status

Show whether this MCP is linked to an AVAS customer account.

start_phone_login

Send an AVAS login OTP to an existing customer's Maldives phone number.

verify_phone_login

Verify the AVAS OTP previously sent by start_phone_login.

list_delivery_addresses

List saved delivery addresses for the linked AVAS account.

get_menu

Load a merchant menu using the linked customer and delivery context.

add_to_cart

Add a canonical CartRow locally; a cart may contain only one merchant.

update_cart_item

Update local cart quantity; use remove_cart_item to delete.

remove_cart_item

Remove one local cart row.

view_cart

View the persisted local cart.

clear_cart

Clear local cart and checkout artifacts; no network request is made.

quote_cart

Calculate an authenticated cart quote. This calls CalculationSalesOrder but never saves.

stage_receipt

Validate and privately copy a PNG/JPEG receipt locally. Does not upload.

upload_receipt

Upload the staged receipt only with the exact displayed confirmation phrase.

prepare_order

Freeze the current quote and order details into an immutable confirmation preview.

submit_order

Validate then place the frozen order exactly once. Ambiguous saves are never retried.

track_deliveries

List and track the linked customer's active AVAS orders and delivery state.

delivery_spending_report

Summarize recorded AVAS spending by restaurant, food type, and delivery fees.

// 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.
configAVAS_STATE_DIRlocal private state override
🔐 secretAVAS_ACCESS_TOKENapproved backend token, if required
configAVAS_ENVIRONMENTdefaults to LIVE
// 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

21/21 tools missing one or more hints — get_client_metadata (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_restaurants (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_restaurant (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — clear_cart deletes at line 578 (try: path.unlink())

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

15/21 tool handlers declare input schemas (71%)

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

Tool handlers catch errors

Only 3/21 tool handlers wrap calls in try/catch (14%)

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 6 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 Verified](https://m8ven.ai/badge/mcp/rayyan011/avasfood-mcp?variant=verified)](https://m8ven.ai/mcp/rayyan011/avasfood-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: df88d8178c21b93b94fc6031fbc9ba7444a04a86
code hash: 30d5472aa7c0bec980b8759d54d99455e60711811a3fa9e74f71844bc0b7bb11
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