Skip to content

MCP servers › dev.danielhan.asolens › mcp

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

dev.danielhan.asolens/mcp

ASOLens MCP server: App Store ranks, competitors and weaknesses, from your own machine — the publisher's description

4 of 6 record checks metRead-only · tools listed 2026-10-23Topic: commerce-and-marketing · AI-classifiedPricing: free · AI-classifiedversion 0.4.1MITstandard input/output15 tools

Summary

dev.danielhan.asolens/mcp is a local MCP server listed in the official MCP registry at version 0.4.1. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 15 tools, 0 resources and 0 prompts.

Record checks

4 of 6 record checks met · 3 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not met: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #6,981 of 15,115 packages by monthly downloads, tied with 13 others
  • Not ranked by stars: no public GitHub repository

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
npm · listed version current
License
MIT
Dependencies
no known high or critical advisories
Tools
15
Described as changing data
1 of 15 toolsAI-classified
Topic
commerce-and-marketingAI-classified
Pricing
freeAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 1 tool is described as changing something (snapshot_save): our AI model's reading of the descriptions, not something we tested. We did not call it.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.4.1, published 2026-10-13 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-13 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
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.4.1 (published 2026-10-13).

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

What it is

What does this server offer?

Observed inventory
15tools
0resources
0prompts

1 of 15 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

  • find_appon 1 other serverreads or searches

    “Looks up an app by id, App Store URL, or name and returns candidate matches with rating and developer info.”

    3 inputs, 1 required
    • querystringrequired“App name or search text to look up on the App Store.”
    • countrystring“Two-letter App Store storefront country code, e.g.”
    • limitinteger“Maximum matches to return for a name search (max 200, Apple's own ceiling).”
  • app_snapshoton 1 other serverreads or searches

    “Resolves an app by id, App Store URL, or name and returns its current listing data plus the developer's other apps in this storefront.”

    2 inputs, 1 required
    • appstringrequired“App to resolve: a numeric App Store id, an App Store URL, or an app name.”
    • countrystring“Two-letter App Store storefront country code, e.g.”
  • search_ranksreads or searches

    “Ranked apps for one keyword in one country, as the App Store lists them (fetched from this machine; cached for the UTC day).”

    3 inputs, 1 required
    • keywordstringrequired“Search keyword to rank apps for.”
    • countrystring“Two-letter App Store storefront country code, e.g.”
    • topinteger“How many ranked entries to return, most-relevant first (max 250 — the ceiling Apple's search returns).”
  • keyword_ranksreads or searches

    “Looks up where one app ranks for a list of keywords, in one or more storefronts, with day-over-day trend where available.”

    7 inputs, 1 required
    • appstringrequired“App to check: a numeric App Store id, an App Store URL, or an app name.”
    • pairsarray“Explicit keyword/country pairs instead of the keywords x countries cross product.”
    • keywordsarray“Keywords to check this app's rank for (max 50; keywords x countries must not exceed 25 pairs total).”
    • countriesarray“Storefront country codes to check, up to 8, paired with every entry in `keywords`.”
    • variantsboolean“For every keyword with an accent on a Latin, Greek or Cyrillic letter, ALSO look up the stripped spelling and return the two side by side in one row, with iden…”
    • coverageboolean“For YOUR OWN app (App Store Connect credentials required), report which of each keyword's words actually appear in the text Apple indexes -- name, subtitle and…”
    • depthboolean“Add autocompleteDepth (how many App Store autocomplete suggestions begin with the keyword) to each row, and to each variant when variants is on.”
  • compare_queriesreads or searches

    “Runs two keywords in one storefront and reports how much their ranked results overlap.”

    5 inputs, 2 required
    • astringrequired“First search keyword.”
    • bstringrequired“Second search keyword, the one to compare against.”
    • countrystring“Two-letter App Store storefront country code, e.g.”
    • appstring“Optional app (id, URL, or name) to also report the rank of in each result set, so you can see the rank difference and the overlap that qualifies it together.”
    • topinteger“How deep to compare the two ranked lists (default 25).”
  • my_listingreads or searches

    “Reads YOUR OWN app's indexed listing text -- name, subtitle and the keywords field -- from App Store Connect, per locale.”

    2 inputs, 1 required
    • appstringrequired“Your app: a numeric App Store id, an App Store URL, or a bundle id.”
    • countrystring“Two-letter storefront country code.”
  • audit_keywordsreads or searches

    “Tests every word in YOUR OWN keywords field by searching a phrase where that word is the distinguishing one -- an anchor your app certainly covers, plus the word under test ('matemática' + 'escola').”

    5 inputs, 1 required
    • appstringrequired“Your app: numeric App Store id, App Store URL, or bundle id.”
    • countrystring“Storefront to test in, e.g.”
    • anchorstring“The context word each probe is built from.”
    • probesarray“Override the generated probe for specific words, e.g.”
    • suggestionsboolean“Include, per word, what App Store autocomplete says people typing that word are actually looking for.”
  • compare_marketson 4 other serversreads or searches

    “Runs the keyword-field audit across several storefronts at once and puts them side by side: how much of your keyword field places in each, your rating count there, and the competitor median with its …”

    4 inputs, 2 required
    • appstringrequired“Your app: numeric App Store id, App Store URL, or bundle id.”
    • countriesarrayrequired“Storefronts to compare, up to 8.”
    • anchorsarray“Per-market anchor overrides, e.g.”
    • probesarray“Per-market probe overrides, e.g.”
  • snapshot_savecreates or changes datadescribed as changing data

    “Captures a named, kept measurement of a keyword set: rank (including null, which is a value here), resultCount, the top 10 app ids, keyword coverage with the listing version it was read from, and you…”

    5 inputs, 2 required
    • namestringrequired“Name to save under, e.g.”
    • appstringrequired“The app to record ranks for: numeric App Store id, App Store URL, or name.”
    • keywordsarray“Keywords to capture in every one of `countries` (a cross product).”
    • countriesarray“Storefronts to capture in, paired with every entry in `keywords`.”
    • pairsarray“Explicit keyword/country pairs, instead of the keywords x countries cross product.”
  • snapshot_diffon 2 other serversreads or searches

    “Compares two named snapshots keyword by keyword: rank before and after (null included), how the result set size changed, which apps entered or left the top 10, and your ratings against the competitor…”

    2 inputs, 2 required
    • beforestringrequired“Name of the earlier snapshot.”
    • afterstringrequired“Name of the later snapshot.”
  • niche_reporton 2 other serversreads or searches

    “Builds a competitive report across a set of keywords: the union of top-ranked apps, a weakness score per competitor, difficulty per keyword, and gaps for your own app.”

    9 inputs, 1 required
    • keywordsarrayrequired“Keywords defining the niche (max 30).”
    • countrystring“Two-letter App Store storefront country code, e.g.”
    • appstring“Your own app, to compare against competitors and compute gaps: id, URL, or name.”
    • namestring“Name for this niche; required (together with save: true) to save it for later reuse.”
    • topinteger“How many top-ranked apps per keyword to include in the report.”
    • saveboolean“If true, saves this niche definition for later reuse -- requires name to also be given, otherwise nothing is saved (see saved/savedReason in the response).”
    • include_inputsboolean“If true, every modelled value (weakness, difficulty, ownTrend, volume) also includes the raw inputs it was computed from.”
    • volumeboolean“DataForSEO's Apple keyword dataset covers the 'us' storefront ONLY -- in every other storefront volume comes back unavailable saying exactly that, at no cost a…”
    • depthboolean“Fetch App Store autocomplete for each keyword and report autocompleteDepth: how many suggested queries begin with that keyword.”
  • low_star_reviewsreads or searches

    “Fetches recent low-star reviews for an app so you can read what's actually bothering users; theme extraction is left to the caller.”

    4 inputs, 1 required
    • appstringrequired“App to fetch reviews for: a numeric App Store id, an App Store URL, or an app name.”
    • countrystring“Two-letter App Store storefront country code, e.g.”
    • maxStarsinteger“Only include reviews with this star rating or lower.”
    • limitinteger“Maximum number of reviews to return.”
Show 3 more tools
  • suggest_keywordson 2 other serversreads or searches

    “Returns App Store autocomplete suggestions for a search term, showing what people actually search for -- the way to check a keyword's intent is what you assume (e.g.”

    2 inputs, 1 required
    • termstringrequired“Search term to get App Store autocomplete suggestions for.”
    • countrystring“Two-letter App Store storefront country code, e.g.”
  • price_keywordsreads or searches

    “Looks up DataForSEO search volume for keywords you already have, by naming each one to the vendor.”

    4 inputs, 1 required
    • keywordsarrayrequired“The keywords to price.”
    • countrystring“Two-letter App Store storefront country code.”
    • appsarray“Competitor app ids to price through.”
    • max_appsinteger“How many competitor apps to query.”
  • keyword_table

    “Builds a table of your saved keywords with current rank, difficulty and trend, refreshing today's data by default.”

    7 inputs
    • countrystring“Two-letter App Store storefront country code, e.g.”
    • appstring“Your own app, to compute rank/trend against in the table: id, URL, or name.”
    • refreshboolean“Re-fetch today's rank data for each saved keyword that hasn't been refreshed yet today, before building the table.”
    • addarray“Keywords to save before building the table (max 50 - each triggers a live App Store search when refresh is true, which it is by default).”
    • notesarray“Notes to attach to already-saved keywords, applied before the table is built.”
    • volumeboolean“DataForSEO's Apple keyword dataset covers the 'us' storefront ONLY -- in every other storefront volume comes back unavailable saying exactly that, at no cost a…”
    • depthboolean“Fetch App Store autocomplete for each keyword and report autocompleteDepth: how many suggested queries begin with that keyword.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 15 tools
Says what it returns
100% of 15 tools
States limits, defaults or errors
53% of 15 tools
Says when to use it
38% of 13 tools
Items covered per tool
3.0 of 4 on average

Counted from the listing

Parameters with a description
100% of 64
Tools with a description
100% of 15
Typical description length
449 characters

The tool set

Counted from the listing

Tools
15
Size of the list
about 7,935 tokens for an agent to load (characters ÷ 4)
Naming
15 of 15 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 15 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @asolens/mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@asolens/mcp@0.4.1"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@asolens/mcp@0.4.1"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@asolens/mcp@0.4.1"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@asolens/mcp@0.4.1"]}'
Claude Code
claude mcp add --transport stdio mcp -- npx -y @asolens/mcp@0.4.1
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @asolens/mcp@0.4.1
  • Optional settings the entry also lists (left out above): ASC_API_ISSUER_ID, ASC_API_KEY_ID, ASC_API_PRIVATE_KEY_PATH, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

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.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.4.1
Latest stable
0.4.1
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-10-24 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-lXtl/Bqw6RLd5VDmw…
Signature
signed
License
MIT

Source: the package registry · 2026-10-22.

Usage

Downloads
306 in the last month

Source: api.npmjs.org · 2026-10-22.

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 saysWe foundResultSource · date
Published package can be startedStarted and answeredmatchesour test · 2026-10-23
Version 0.4.1 on npmExists and can be installedmatchesnpm · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

4 of 6 record checks met · 3 do not apply

  • #6,981 of 15,115 packages by monthly downloads, tied with 13 others
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. 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 dev.danielhan.asolens/mcp

Answered from the data above

Is dev.danielhan.asolens/mcp safe to install?

We do not rate servers as safe or unsafe. 4 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 1 of its tools describes changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is dev.danielhan.asolens/mcp free to use?

Its website (asolens.danielhan.dev/) describes a free pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Has dev.danielhan.asolens/mcp been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can dev.danielhan.asolens/mcp do?

It lists 15 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.

Can dev.danielhan.asolens/mcp change or delete data?

1 of its tools says in its description that it creates, edits, deletes, sends or runs something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Is the listed version current?

Yes. The registry lists 0.4.1, the latest stable release on npm.

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.

Similar servers

Same topic · AI-read

Active servers whose topic is also “commerce-and-marketing” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

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

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

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

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 10
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
Does not apply to this server · 6
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

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.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 22,550 msConnected after 0 redirects.
  3. Read the inventory: 15 tools, 0 resources, 0 prompts.
  4. 25,445 msFinished: 2 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
AI-classified · 2026-10-23
Pricing modelAI-classified
free
read from asolens.danielhan.dev/ · 2026-10-23

“Free. No ASOLens account. It runs on your machine and keeps its history in a local SQLite file. Needs Node.js 22.13 or newer.”

Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
standard input/output
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
package registry · 2026-10-22
Integrity hash
declared (sri)
package registry · 2026-10-22
Signature / provenance
signed
package registry · 2026-10-22
Dependency advisories
none known
npm audit · 2026-10-24
Popularity
306 downloads a month
package registry · 2026-10-22
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
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. “dev.danielhan.asolens/mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/dev.danielhan.asolens/mcp

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: 4 of 6 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/dev.danielhan.asolens/mcp)](https://protocolprobe.com/mcp/servers/dev.danielhan.asolens/mcp)

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