MCP servers › io.github.farssaadeldin7-ux › diagnose-by-sound

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.farssaadeldin7-ux/diagnose-by-sound

Turn a described vehicle noise into a ranked, testable differential diagnosis with a safety... — the publisher's description

4 of 5 record checks metversion 0.1.3JavaScriptstandard input/output

Summary

io.github.farssaadeldin7-ux/diagnose-by-sound is a local MCP server listed in the official MCP registry at version 0.1.3.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: not an npm or PyPI package
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: MCP bundle
Repository: public
Last tested: 2026-10-23

Add to your client

How fresh this is

Live-tested: attempted, see below
Last tested: 2026-10-23
Latest version: 0.1.3, published 2026-10-20 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-20 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.1.3 (published 2026-10-20).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

How do I add it to my client?

Config from the registry entry

No config: the MCP bundle is a file to install in a client that supports bundles, not a command.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started, but no session could be opened	no session	our test · 2026-10-23
Repository github.com/farssaadeldin7-ux/claude-plugin-suite	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.farssaadeldin7-ux · 14 servers
GitHub owner: a personal account (farssaadeldin7-ux)

Repository: github.com/farssaadeldin7-ux/claude-plugin-suite
Stars: 0
Repository age: 31–90 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: not an npm or PyPI package
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.farssaadeldin7-ux/diagnose-by-sound

Answered from the data above

Is io.github.farssaadeldin7-ux/diagnose-by-sound safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.farssaadeldin7-ux/diagnose-by-sound been security tested?

We tried, but no check could run. None of the 18 checks that apply to it could be exercised. No session could be opened when we tried, so no check could run. No security verdict is published before verification.

Does io.github.farssaadeldin7-ux/diagnose-by-sound publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.farssaadeldin7-ux/diagnose-by-sound?

In github.com/farssaadeldin7-ux/claude-plugin-suite, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

No session

No session could be opened when we tried, so no check could run. No security score is given; a check we did not run is never counted as passed.

Why not security-tested: The package's process closed before a session opened, and the recorded output does not show whether the cause was ours or the package's. — cause not determined

The 18 checks at a glanceour test · 2026-10-23

Inventory: not run · no session
Hidden instructions: not run · no session
Real execution: not run · no session
Secret leak: not run · no session
Internal addresses: not run · no session
Unconfirmed changes: not run · no session
Bad input: not run · no session
Model requests: not run · no session
Sensitive questions: not run · no session
Folder boundary: not run · no session
Log leaks: not run · no session
Hidden content: not run · no session
Fake assistant turns: not run · no session
Token passthrough: not run · no session
Token audience: not run · no session
Sign-in redirect: not run · no session
Consent handling: not run · no session
Sign-in metadata: not run · no session

0 exercised18 not run (reason given)0 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). None of the 18 checks that apply to it could be exercised. We do not publish security-check outcomes for named servers.

Not run, with the reason · 18

1Inventory
tool-listReads the declared tools, resources and prompts.No session could be opened with the server, so no check could run.not run · no session
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.No session could be opened with the server, so no check could run.not run · no session
3Real execution
real-executionCalls a tool and checks what really happens.No session could be opened with the server, so no check could run.not run · no session
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.No session could be opened with the server, so no check could run.not run · no session
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.No session could be opened with the server, so no check could run.not run · no session
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.No session could be opened with the server, so no check could run.not run · no session
7Bad input
error-handlingSends bad input and watches how the server answers.No session could be opened with the server, so no check could run.not run · no session
8Model requests
samplingChecks whether the server asks the client's model to act for it.No session could be opened with the server, so no check could run.not run · no session
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.No session could be opened with the server, so no check could run.not run · no session
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.No session could be opened with the server, so no check could run.not run · no session
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.No session could be opened with the server, so no check could run.not run · no session
12Hidden content
audience-hidingChecks resources that hide content from the user.No session could be opened with the server, so no check could run.not run · no session
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.No session could be opened with the server, so no check could run.not run · no session
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.No session could be opened with the server, so no check could run.not run · no session
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.No session could be opened with the server, so no check could run.not run · no session
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.No session could be opened with the server, so no check could run.not run · no session
17Consent handling
confused-deputyChecks consent handling when one service acts for another.No session could be opened with the server, so no check could run.not run · no session
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No session could be opened with the server, so no check could run.not run · no session

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox
No session could be opened.
390 msFinished: 0 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

no value

No value: the two AI models (Gemini and Claude) disagreed, so neither answer is shown.

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

JavaScript

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

not checked

not read (no session)

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

mcpb

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here

Integrity hash

does not apply

package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here

Signature / provenance

does not apply

package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here

Dependency advisories

not checked

only npm and PyPI packages are audited

Popularity

does not apply

package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here

Publisher signals

owner: a personal account · repository age: 31–90 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.farssaadeldin7-ux/diagnose-by-sound: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.farssaadeldin7-ux/diagnose-by-sound

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.farssaadeldin7-ux/diagnose-by-sound)](https://protocolprobe.com/mcp/servers/io.github.farssaadeldin7-ux/diagnose-by-sound)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology