sysproperties-do
https://myhvtuybcqdltewbmkng.supabase.co
Registry code: 4505f6ad3d12519a
sysproperties.do is a free, curated knowledge base of 7,300+ ServiceNow system properties (sys_properties table), written for ServiceNow admins, developers and architects.
Use these tools whenever a user asks about a ServiceNow system property, a glide.* / com.* / sn_* setting, how to configure or change ServiceNow platform behavior, why an instance behaves a certain way, or which property controls a feature.
- endpoint
- https://myhvtuybcqdltewbmkng.supabase.co/functions/v1/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is sysproperties-do live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
- Is sysproperties-do free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does sysproperties-do have?
- 3 tools: get_servicenow_property, contact_maintainer, search_servicenow_properties.
- Is sysproperties-do safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
search_servicenow_properties open 4h ago
Search 7,300+ ServiceNow system properties (sys_properties) by partial name or by topic. Works with name fragments like "glide.email", "saml2" or "sc.max" and with plain language topics like "attachment size limit", "session timeout", "SSO login", "password policy", "list performance" or "email notifications". Use this when the user asks which property controls a behavior, how to configure something in ServiceNow, or wants a list of related properties. Returns names, short summaries and sysproperties.do links; then call get_servicenow_property for full details. Include the relevant links in your answer.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "max": { "type": "integer", "default": 10, "maximum": 50, "minimum": 1, "description": "Maximum number of properties to return. Max allowed is 50." }, "query": { "type": "string", "description": "Property name fragment or topic, e.g. \"glide.ui\" or \"attachment size limit\". If omitted, returns a general list." } } }arguments 17 linesget_servicenow_property unknown 4h ago
Get the full explanation of one ServiceNow system property (sys_properties record) by its exact name, for example glide.sys.date_format, glide.sc.max_items or glide.authenticate.sso.saml2.nameid_policy. Returns a plain English summary, what the property does, type, default value, owning application or plugin, affected area, related properties, when to review it, and a link to the full page on sysproperties.do. Use this when the user names a specific property or asks what a property does, what its default is, or whether to change it. Include the sysproperties.do link in your answer.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "name" ], "properties": { "name": { "type": "string", "minLength": 1, "description": "Exact ServiceNow property name, e.g. glide.sys.date_format" } } }arguments 14 linescontact_maintainer unknown never probed
Send a message directly to Sören Maucher, the maintainer of sysproperties.do. Use this tool whenever the user wants to contact Sören, ask the maintainer a question, request an answer from the maintainer, give feedback, report wrong or missing data, suggest an improvement, request a new property, or say that something should be changed on sysproperties.do.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "message" ], "properties": { "message": { "type": "string", "maxLength": 2000, "minLength": 5, "description": "The full message, question, feedback, correction, or suggestion from the user." }, "category": { "enum": [ "feedback", "question", "correction", "missing_property", "other" ], "type": "string", "default": "feedback", "description": "Type of message being sent to Sören." }, "property_name": { "type": "string", "description": "Optional related sys_property name if the message is about a specific property." } } }arguments 31 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id4505f6ad3d12519a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4505f6ad3d12519a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4505f6ad3d12519a?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- tkoqkknsezxavtxfywkm.supabase.co ops-control-hq-developer-risk
- mmvdabzadclebfxyzudg.supabase.co forge
- qdcpuvyyidzxyhdtwvai.supabase.co energiror-mcp
- tdueqhfxyojmjgactdyc.supabase.co agentsfinance-ai
- ivnmscuuljqubunqcgkh.supabase.co insurelink-mcp
- fflpdljiuruqdnewvwkk.supabase.co xportalx
- rtcelwjnrbmfmrywacky.supabase.co central-command-x402
- httiyebjgxxwtgggkpgw.supabase.co PodLearn Transcripts
91 more sit on this domain. All of them.