Skip to content

MCP servers › io.github.tonhowtf › omniget

MCP server · registry snapshot 2026-11-15 · last checked 2026-11-15

omniget MCP server

Registry name io.github.tonhowtf/omniget

by tonhowtf · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Queue, track and diagnose media downloads (yt-dlp sites, torrents) in the OmniGet app — the publisher's description

3 of 5 record checks metversion 1.0.0Rust

Summary

io.github.tonhowtf/omniget is an MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the GitHub account tonhowtf. Its linked repository, github.com/tonhowtf/omniget, belongs to the same GitHub account.

Record checks

3 of 5 record checks met · 4 do not apply

  • not 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

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

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Repository
public
Last tested
not tested

Tool list

Not read: The registry entry declares no package and no remote endpoint, so there is nothing to run. So there is no tool-list size and no result from the three APIs.

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
1.0.0, published 2026-11-14 (registry, as of the 2026-11-15 snapshot)
First listed version
2026-11-14 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-15
Package and repository
checked 2026-11-15

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-14, listed on 2026-11-15 with version 1.0.0 (published 2026-11-14).

Source: the official MCP Registry list on 2026-11-14 and on 2026-11-15.

What it is

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-15. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-15. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-15. Source: read 2026-11-15.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-15. Source: read 2026-11-15.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/tonhowtf/omnigetOpens publiclymatchesapi.github.com · 2026-11-15

Who made it?

Feature #7 · lineage

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

Namespace
io.github.tonhowtf
GitHub owner
a personal account (tonhowtf)
Repository
github.com/tonhowtf/omniget
Stars
14,447
Repository age
181–365 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-11-15; security policy read from GitHub · 2026-11-15.

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

3 of 5 record checks met · 4 do not apply

  • Not metRegistry entry is active and says how to run itThe entry lists no package and no remote address, so a client cannot run it.What changes this check: This check reads the registry entry's status and whether it lists a package or a remote address. Marking an entry deprecated is the publisher's own choice. The registry's documentation says a published version's metadata cannot be changed; a new server.json with a unique version string is how an entry is updated. Versioning published MCP servers
  • 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.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierThe entry lists no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnThe entry lists no package.
  • Does not applynpm package carries build provenance (attestation)The entry lists no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesThe entry lists no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-15 (security policy 2026-11-15). 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, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.tonhowtf/omniget

Answered from the data above

Who publishes io.github.tonhowtf/omniget?

The registry ties the namespace io.github.tonhowtf to the GitHub account tonhowtf; only its owner can publish under it. Its linked repository, github.com/tonhowtf/omniget, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.tonhowtf/omniget safe to install?

We do not rate servers as safe or unsafe. 3 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.tonhowtf/omniget been security tested?

No. The registry entry declares no package and no remote endpoint, so there is nothing to run.

Does io.github.tonhowtf/omniget 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.tonhowtf/omniget?

In github.com/tonhowtf/omniget, 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

Has it been tested?

Feature #1

The registry entry declares no package and no remote endpoint, so there is nothing to run. — the server's own choice

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
pending: added at the next monthly refresh
listed 2026-11-15; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-15
Hosting type
not stated
entry declares neither packages[] nor remotes[], so no delivery method is stated
MCP capability
not checked
not read (no session)
Transport
not stated
no packages[] or remotes[] to carry a transport
Required credentials
not stated
no packages[] or remotes[] to carry credential declarations
Package registry
not stated
no packages[] and no remotes[], so no delivery method is stated
Freshness
0–30 days
registry updatedAt · 2026-11-15
Lifecycle status
registry · 2026-11-15
License class
not stated
server declares no packages[], so no package registry can be queried
Integrity hash
not stated
server declares no packages[], so no package registry can be queried
Signature / provenance
not stated
server declares no packages[], so no package registry can be queried
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
not stated
server declares no packages[], so no package registry can be queried
Publisher signals
owner: a personal account · repository age: 181–365 days · stars: 1,000 or more
api.github.com · 2026-11-15
Maintenance
api.github.com · 2026-11-15
Environment
not stated
entry declares neither packages[] nor remotes[], so no delivery method is stated

“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.tonhowtf/omniget: MCP server record.” Data checked 2026-11-15. https://protocolprobe.com/mcp/servers/io.github.tonhowtf/omniget

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: 3 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.tonhowtf/omniget)](https://protocolprobe.com/mcp/servers/io.github.tonhowtf/omniget)

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, except for a server whose operator has claimed it and given permission (that server's page says so).

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