Skip to content

MCP servers › com.tektolo › capabilities

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

com.tektolo/capabilities

Deterministic, source-cited rental property tools: turnover estimates and deposit rules by US state. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: data-and-databases · AI-classifiedPricing: freemium · AI-classifiedversion 0.1.0Pythonstreamable HTTP5 tools

Summary

com.tektolo/capabilities is a remote MCP server listed in the official MCP registry at version 0.1.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 5 tools, 5 resources and 0 prompts.

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: a remote server publishes no download figure
  • 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
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
5
Described as changing data
1 of 5 toolsAI-classified
Topic
data-and-databasesAI-classified
Pricing
freemiumAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 1 tool is described as changing something (deposit_settlement_settle): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. 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.1.0, published 2026-10-10 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-10 (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.1.0 (published 2026-10-10).

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
5tools
5resources
0prompts

1 of 5 tools are described as changing something (creating, editing, deleting, sending or running).

  • deposit_settlement_settleon 1 other serverdescribed as changing data

    “Settles a US residential security deposit after move-out under the state's statute (50 states and DC) and a covered city's ordinance.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    50 inputs, 3 required
    • client_refsobject“Your own reference ids (e.g.”
    • statestringrequired“US state, 2-letter code (e.g.”
    • citystring“City, for a city overlay where covered (e.g.”
    • deposit_usdnumber or stringrequired“Security deposit held, dollars.”
    • monthly_rent_usdnumber or string“Monthly rent, for the deposit cap check.”
    • building_unitsinteger“Units in the building.”
    • move_in_onstring“Tenancy start (YYYY-MM-DD).”
    • tenancy_ended_onstring“When the tenancy actually ended (YYYY-MM-DD): the lease's end, or an earlier termination or accepted surrender.”
    • lease_end_onstring“Day the lease was scheduled to end (YYYY-MM-DD), when it differs from when the tenancy actually ended (a broken lease).”
    • vacated_onstringrequired“Day the tenant moved out and returned possession (YYYY-MM-DD).”
    • forwarding_address_received_onstring“Day you received the tenant's written forwarding address (YYYY-MM-DD).”
    • tenant_gave_forwarding_addressboolean“False when the tenant never gave a forwarding address in writing (not just 'not yet known').”
    • demand_received_onstring“Day you received the tenant's demand for the deposit (YYYY-MM-DD; written in Oklahoma, by first-class mail in Maryland 8-203(h)).”
    • new_tenant_moved_in_onstring“Day a new tenant moved in, if the unit was re-rented (YYYY-MM-DD).”
    • new_tenant_rent_usdnumber or string“Monthly rent the new tenant pays (with new_tenant_moved_in_on): the rent received for overlapping days is credited against rent claimed for them.”
    • statement_sent_onstring“Day you sent (or delivered) the itemized statement (YYYY-MM-DD).”
    • claim_notice_sent_onstring“Day you sent the written notice of intent to impose a claim on the deposit (YYYY-MM-DD).”
    • lease_return_daysinteger“Return period the lease sets, in days, where the statute lets a lease set one (Colorado up to 60, Idaho up to 30, Maine shorter).”
    • tenant_gave_proper_noticeboolean“A termination notice that meets the statute was given (Alaska: 14 days instead of 30 when nothing is deducted for damage).”
    • interest_paid_throughstring“Interest already paid or credited to the tenant up to this day (annual-payment rules: San Francisco, Los Angeles, Berkeley, Connecticut, Massachusetts, ...): i…”
    • nonstandard_provision_signedboolean“Wisconsin: the tenant signed a separate NONSTANDARD RENTAL PROVISIONS document covering the charge (ATCP 134.06(3)(b)); false makes such charges 'no'.”
    • pet_deposit_usdnumber or string“The part of deposit_usd that is a pet deposit (outside the cap in Missouri, Alabama, North Dakota and Saint Paul; allowed on top of it up to one month in Hawai…”
    • tenant_age_62_plusboolean“The tenant is 62 or older (Connecticut: a one-month cap).”
    • tenant_age_60_plusboolean“A person 60 or older occupies the unit (New Hampshire 540-A:5, I: the owner-occupied exemption does not reach the unit).”
    • small_landlordboolean“California AB 12 small landlord (a natural person or an LLC of natural persons owning at most two properties with at most four units; not for a service member)…”

    and 25 more not listed here.

  • deposit_settlement_ruleson 1 other serverreads or searches

    “Looks up the security deposit rules (deposits only) for one US state, with a covered city's deposit ordinance (Chicago, San Francisco, Berkeley, Los Angeles, Seattle, Portland, Minneapolis, Saint Pau…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs, 1 required
    • statestringrequired“US state, 2-letter code or name (e.g.”
    • citystring“Optional city for its overlay (e.g.”
    • as_ofstring“Optional date (YYYY-MM-DD): show the law in force on that day, for a past move-out the day the tenancy ended.”
    • auditboolean“Also return the run record and input/result hashes (an audit trail).”
    • expect_rulesetstring“Optional.”
    • serve_pinnedboolean“Optional, with expect_ruleset.”
  • property_turnover_quick_estimateon 1 other servergenerates content

    “Estimates what it costs to turn over a US rental unit after move-out; the first tool for a turnover estimate.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    17 inputs, 3 required
    • client_refsobject“Your own reference ids (e.g.”
    • zipstringrequired“The user's 5-digit US ZIP code.”
    • bedroomsintegerrequired“0 for a studio.”
    • bathroomsnumber or stringrequired“Half baths count as 0.5.”
    • issuesarray“What was found in plain English, e.g.”
    • unit_typestring“Single-family homes and townhomes get house-sized defaults (floor area, locks).”
    • sq_ftinteger“Interior sq ft.”
    • year_builtinteger“Drives lead-paint (pre-1978) handling.”
    • carpetboolean“Is there wall-to-wall carpet?”
    • walk_datestring“The walk-through date; dated or aged items are judged against it.”
    • profilestring“minimum (rent-ready basics) | standard | premium (higher finish).”
    • price_tierstring“bulk_contract (portfolio contract prices) | pm_vendor (default: a property manager buying turns from local vendors) | retail_one_off (an owner hiring one contr…”
    • detailstring“summary (default, small) or full (every line).”
    • retainboolean“Optional (contract 0.5.1).”
    • auditboolean“Also return the run record and input/result hashes (an audit trail).”
    • expect_rulesetstring“Optional.”
    • serve_pinnedboolean“Optional, with expect_ruleset.”
  • property_turnover_scopeon 1 other servergenerates content

    “Turns move-out inspection findings for a US rental unit into a priced make-ready scope.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    15 inputs, 1 required
    • client_refsobject“Your own reference ids (e.g.”
    • propertyobjectrequired“The unit: ZIP, size, type and year built.”
    • findingsarray“Move-out inspection findings, one per observed condition, coded.”
    • standardsobject“Finish profile, price tier and overrides.”
    • rate_cardarray“Your own prices by trade or task; they replace the regional library prices.”
    • trade_vendorsobject“Vendor (name, contact) to put on each trade's lines.”
    • constraintsobject“Target ready date, whether the unit is occupied, access notes.”
    • tax_ratenumber or string“Applied to all lines, e.g.”
    • decisionsarray“Approve, decline or defer lines or findings from an earlier scope.”
    • readstring“Deprecated and ignored: scope reads no free text.”
    • retainboolean“false: keep none of this request's text.”
    • detailstring“summary (small): totals, trade scopes, lines tied to findings.”
    • auditboolean“Also return the run record and input/result hashes (an audit trail).”
    • expect_rulesetstring“Optional.”
    • serve_pinnedboolean“Optional, with expect_ruleset.”
  • property_turnover_issue_codeson 1 other serverreads or searches

    “The issue-code catalog for rental-unit turnover findings (group.issue codes such as carpet.pet_urine).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    10 inputs
    • client_refsobject“Your own reference ids (e.g.”
    • qstring“Words to search for in the codes, names, aliases, descriptions and examples, e.g.”
    • groupstring“Only codes in this group, e.g.”
    • limitinteger“Most codes to return.”
    • include_aliasesboolean“Also return aliases in the short list (search hits always carry them).”
    • querystring“Older name for q; use q.”
    • areastring“Older name for group; use group.”
    • auditboolean“Also return the run record and input/result hashes (an audit trail).”
    • expect_rulesetstring“Optional.”
    • serve_pinnedboolean“Optional, with expect_ruleset.”

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. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. 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 5 tools
Says what it returns
100% of 5 tools
States limits, defaults or errors
0% of 4 tools
Says when to use it
25% of 4 tools
Items covered per tool
2.6 of 4 on average

Counted from the listing

Parameters with a description
100% of 98
Tools with a description
100% of 5
Typical description length
728 characters

The tool set

Counted from the listing

Tools
5
Size of the list
about 38,305 tokens for an agent to load (characters ÷ 4)
Naming
5 of 5 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 5 of 5 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 remote endpoint (Streamable HTTP)

We connected to this URL 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.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://tektolo.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "capabilities": {
      "url": "https://tektolo.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "capabilities": {
      "type": "http",
      "url": "https://tektolo.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"capabilities","type":"http","url":"https://tektolo.com/mcp"}'
Claude Code
claude mcp add --transport http capabilities https://tektolo.com/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://tektolo.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • 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.

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
Remote endpoint tektolo.com/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23
Repository github.com/tektolo/skillsOpens publiclymatchesapi.github.com · 2026-10-22

Who made it?

Feature #7 · lineage

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

Namespace
com.tektolo · 2 servers
GitHub owner
an organization (tektolo)
Repository
github.com/tektolo/skills
Stars
0
Repository age
0–30 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-22; 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.

Same tools as other registry entries

Tool lists read · names compared

Its 5 tools have exactly the same names as the tools of 1 other registry entry (all published under the same registry namespace). Their tool descriptions are also word for word the same.

This can be one publisher's family of servers or one template reused under many names. It is a fact about the published tool lists, not a judgement of the publisher and not a safety finding; we compared tool names, not code.

Shared tool names:

deposit_settlement_rulesdeposit_settlement_settleproperty_turnover_issue_codesproperty_turnover_quick_estimateproperty_turnover_scope

The other entries

All groups of servers with identical tool lists

Source: our read-only reads of each server's tool list · 2026-10-23. No tool was called.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • 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) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

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 com.tektolo/capabilities

Answered from the data above

Is com.tektolo/capabilities 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. 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 com.tektolo/capabilities free to use?

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

Does com.tektolo/capabilities need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.tektolo/capabilities been security tested?

Partly. 3 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can com.tektolo/capabilities do?

It lists 5 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 generate content. We did not call any tool, so this describes the text, not the behaviour.

Can com.tektolo/capabilities 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.

Does com.tektolo/capabilities 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 com.tektolo/capabilities?

In github.com/tektolo/skills, 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.

Similar servers

Same topic · AI-read

Active servers whose topic is also “data-and-databases” 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 (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. 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: exercised
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

3 exercised11 not run (reason given)4 not applicable

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

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 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 opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 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 a read-only session with the server's remote endpoint
  2. 1,207 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 5 tools, 5 resources, 0 prompts.
  4. 6,874 msFinished: 3 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
freemium
read from tektolo.com/pricing · 2026-10-23

“Agents and software get a free tier of 20 calls a day, then $0.02 a call.”

Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
prompts, resources, tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-22
Maintenance
api.github.com · 2026-10-22
Environment
the publisher's infrastructure
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. “com.tektolo/capabilities: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/com.tektolo/capabilities

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

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.tektolo/capabilities)](https://protocolprobe.com/mcp/servers/com.tektolo/capabilities)

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